[ ] 🥚 Project Definition and Scope: As a group, you can agree on what you
are trying to build, and can clearly describe the project using a README
and a repository description.
🥚 Project Constraints: As a group you can define project constraints by
discussing your strengths, weaknesses and context. You can set these types of
constraints:
[x] External: constraints that come from outside your group
[x] Internal, Involuntary: constraints that come from within your group,
but your group did not decide to have.
[x] Internal, Voluntary: constraints your group decides on to improve the
quality of your development process and final software.
[x] 🥚 Communication Plans: You can work with your group mates to agree on
a communication plan to follow during development.
[x] 🥚 Communicating Challenges: During development you can discuss with
your group when ...
you are blocked and need help the agreed channels of communication.
your schedule or availability changes
you are having trouble getting along with each other
[x] 🥚 Using a Backlog: You can develop from a backlog of features
organized by priority:
must-have
should-have
could-have
[x] 🥚 Follow a Development Strategies: You can follow a development
strategy to understand the code required for must-have user stories.
[x] 🥚 Create Issues From a Dev Strategy: You can create issues for user
stories in your project based on the development strategy.
🥚 Retrospective: Your group can complete a retrospective to ...
[x] assess how well you worked as a group
[ ] find ways to improve in the next project
[x] compare your plan to the reality of developing your website
🐣 Claiming and Completing Issues: You can claim issues from the TODO
column of a project board and ...
[x] track your progress with the project board
[x] develop your code locally on a separate branch
[x] send a PR that passes CI checks and meets the requirements
[x] 🐣 Code Review: You can both review a group mate's PR, and
productively participate in a review of your own code.
[ ] 🐣 Match a Design & Acceptance Criteria: When developing your tasks,
you can write code that matches the project's Wireframe and meets your
issue's Acceptance Criteria.
[x] 🥚 Write User Personas: As a group you can describing your site's
users with User Personas, and you can use the personas to plan your
website from the user's perspective.
[x] 🥚 Write User Stories: Given a working web page, you can describe it
with user stories and acceptance criteria for each user story.
[x] 🐣 Write a Backlog: After listing all the user stories for a web page,
you can organize them into a Backlog by priority: must-have,
should-have and could-have
[x] 🐣 Create a Prioritized Design: Using your backlog and the original
site as a guide, you can create a Wireframe of the site your group will
build. You can use different colors and comments to indicate a priority
for each component in the Wireframe.
[x] 🐣 Write a Development Strategies: You can translate your Wireframe
and Backlog into a Development Strategy for the must-have user stories.
[x] 🐣 Adjusting the Backlog: As a group you can agree to changes in the
backlog when necessary.
[x] 🐣 Adjusting the Design: As a group you can agree on changes to the
design during the development process when it becomes clear your old
design needs updating.
[x] 🐣 Updating the Project Board: You can manage the project board by
adding, removing or updating issues when necessary. This includes changing
labels, milestones, or assignees when necessary.
Agile Methods
[x] Requirement definition & analysis of concept
[x] Planning of sprint
[x] Collaborative design development
[x] Create & implement
[x] Review & monitor
Agile Methodology
[x] User persona an imaginary audience. It helps us to understanding the targeted group audience. Without user persona we can't make wireframe.
[x] User stories/backlog is sorted by PRIORITY! It contains needs of the audience. Must have, Should have and Could have.
[x] Acceptance criteria example: A user can't submit a form without completing all mandatory
[x] Wireframe must be create based on user story/backlog.
[x] Development strategy converting the must have or priority needs of audience to coding phase.
[x] Retrospective intern feedback in group. It's about BEHAVIOR not people. We are not allowed to pointing someone in this session. Mostly done at the end of the week.
[x] Stand-up meeting is a brief daily meeting. It's like updating our work project to the group, what we've done, what we are currently busy with or even which problem do we have about the task. Mostly done for max 15mins
[x] Constraints consist of planning, availability timetable, template file, code of conduct.
Planning
[x] Make a group availability timetable
[x] Set-up meeting hours for the whole week based on availability timetable
[x] Creating repo using template
[x] Protecting master repo
[x] Set the repo live/live url
[x] Adding collaborator
[x] Creating additional labels
[x] Creating Project Board and organising it
[x] Creating issue to be put in PB
[x] Discussing README content
[ ] Discussing code of conduct
[x] Discussing user persona
[x] Discussing backlog
[x] Discussing design
[x] Creating wireframe
[ ] Retrospective
Week 1 (April 2nd, 2023)
I Need Help With:
Nothing for a moment
What went well?
[x] Understanding the 3 software development methodologies
[x] Understanding Agile development methodologies in depth
Learning Objectives
0. Developing HTML & CSS
Practice with the skills, tools, and workflows you will need to efficiently develop websites written with HTML & CSS.
npm run format
to format all the code in your repositorynpm run lint:css
script to find mistakes in your CSS, and you can fix the mistakes.npm run validate:html
script to find mistakes in your CSS, and you can fix the mistakes.1. Following Plans
[ ] 🥚 Project Definition and Scope: As a group, you can agree on what you are trying to build, and can clearly describe the project using a README and a repository description.
2. Writing Plans
3. Adapting Plans
Agile Methods
Agile Methodology
Planning
Week 1 (April 2nd, 2023)
I Need Help With:
Nothing for a moment
What went well?
What went less well?
Lessons Learned
Sunday Prep Work
Week 2 (April 13, 2023)
I Need Help With:
Nothing for a moment
What went well?
What went less well?
Lessons Learned
Sunday Prep Work
Not yet.