Maurice: Agile Development, Week 1, 2 & 3

[mauricemat]

Study Plan

• Agile Development
• Sprint Planning
• User Stories
• Website Planning
• Working Together
• Code Review
• HTML & CSS
• Agile is not Perfect
• Class Recordings

---

Collaborating in a group

• You can work with your group mates to agree on a communication plan.
• As a group you can define project constraints by discussing your strength's, weaknesses and context.
• During development you can ask your group for help when you need it using the agreed channels of communication.
• During development you communicate any changes in your personal situation that will impact the group.
• When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.

Planning

• You can work in a group to plan a multi-page website written with HTML & CSS:
• You can understand a web page's users by creating user personas.
• You can work together to write a backlog of user stories for your personas, organized by priority (must, should, could)
• You can work together to create a simple wireframe with pencil+paper and a basic drawing app like Excalidraw
• You can work together to write a development strategy for must-have user stories.
• You can work together to convert a development strategy into issues on a project board organized with labels and milestones.

Developing

• You can claim a task and manage your progress using the project board columns.
• Your group can use issues to discuss and agree on project changes once development has begun.
• You can use the help-wanted label to ask for help and to find issues that need your help.
• You can manage a separate branch with your work for each issue task.
• You can create a PR that passes CI checks when your task is finished, then assign someone to review it.
• You can review a group member's PR and conduct a code review using the project's checklist

[colevandersWands]

@mauricemat , can you move your check-in to a separate comment like #85? It will make it easier to follow your progress

[mauricemat]

Week 1

• I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

• Resolve lint issues

What went well?

• Create HTML and CSS files
• Design webpages (wireframe)
• Planning the work in group

What went less well?

Lessons Learned

• Practise

Sunday Prep Work

[mauricemat]

Week 3

Check-In

I Need Help With:

• Using CLI in Ubuntu terminal.
• I have not yet seized the particularity of the Agile Development concept in relation to the HYF website project. The organisation and planning of the work seem logical. I don't see the novelty of this concept.

What went well?

• Creating user-personas. (Thanks to the template coach Tamer gave us).
• Understanding the importance of the development strategy and Backlog.
• Planning the work with the whole group.

What went less well?

Lessons Learned

• Practise
• Work (brainstorm) in group

Sunday Prep Work

[colevandersWands]

The organisation and planning of the work seem logical. I don't see the novelty of this concept.

You're still in the planning phase of a short project, the Agileness will become more clear when you start developing. Everyone will be claiming issues and working on their parts, then suddenly you'll find that the plan isn't quite right. As a group you'll need to revise your plan and adjust the website. That's the Agileness

You'll also see the Agileness in longer projects with a client and a user. Your group would be in constant communication with the client and users, always listening to their feedback and adjusting your plans. With each sprint (~2 weeks) your group would revisit the plan before starting the next sprint.

for now you're just learning the basic skills needed to work in an Agile project

[colevandersWands]

PS. next time don't add the checked labels yourself, your coaches use that label to know which issues haven't been checked. If you put it on yourself then we'll think someone has already answered your questions and we won't read your check-in

[mauricemat]

PS. next time don't add the checked labels yourself, your coaches use that label to know which issues haven't been checked. If you put it on yourself then we'll think someone has already answered your questions and we won't read your check-in

Thank you, well noted.

[mauricemat]

The organisation and planning of the work seem logical. I don't see the novelty of this concept.

You're still in the planning phase of a short project, the Agileness will become more clear when you start developing. Everyone will be claiming issues and working on their parts, then suddenly you'll find that the plan isn't quite right. As a group you'll need to revise your plan and adjust the website. That's the Agileness

You'll also see the Agileness in longer projects with a client and a user. Your group would be in constant communication with the client and users, always listening to their feedback and adjusting your plans. With each sprint (~2 weeks) your group would revisit the plan before starting the next sprint.

for now you're just learning the basic skills needed to work in an Agile project

Thank you @colevandersWands for your explanations.