Alina: 03agile-development-week1-3

[AlinaTaoRao]

my fork of the exercises repo: agile-group-3 materials agile-development

Study Plan (Suggested Study)

Curriculum Study Book

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

---

Learning Objectives

• Collaborating: You can effectively work in a group:
• [x] 🥚 You can work with your group mates to agree on a communication plan.
• [x] 🥚 As a group you can define project constraints by discussing your strength's, weaknesses and context.
• [x] 🥚 During development you can ask your group for help when you need it using the agreed channels of communication.
• [x] 🥚 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:
• [x] 🥚 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)
• [x] 🥚 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: Once the project board is set up you can work with your group to develop the website:
• [ ] 🥚 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.

Week 1

• [x] I have pushed my progress to my fork of exercises repo: agile-group-3

Check-In

I Need Help With:

What went well?

What went less well?

Lessons Learned

Sunday Prep Work

[AlinaTaoRao]

Week 1

• [x] I have pushed my progress to my fork of exercises repo: agile-group-3

Check-In

I Need Help With:

What went well?

What went less well?

Lessons Learned

Sunday Prep Work

[AlinaTaoRao]

Week 2

• [x] I have pushed my progress to my fork of exercises repo: hyf-group3

Check-In

I Need Help With: npm spell-check.

1. I clone the group repo
2. create a branch alina-planning-constrains
3. edit contrains.md
4. commit edit
5. run Code Quality Scripts , then I failed at npm spell-check. It looks like this picture below. I think it's a problem with html/css, but I didn't edit any html/css file. By the way, I passed the "lint-and-validate (pull_request)" check. Do I need to fix this problem? How?

What went well?

• user persona
• user story
• backlog

What went less well?

• dev strategy-how to divide branches?
  • each page a branch? then how can 2 person collaborate to develop one page?
  • or each issue a branch(that will be too much branches)?
• design (Figma: from the very beginning)

Lessons Learned

Trust your classmate and understand their situations.

Sunday Prep Work

[arnochauveau]

Hey @AlinaTaoRao concerning the npm spell-check issue: what version of node are you running (you can check by running node -v)? I had some issues as well while trying to run the command on my device. After using a newer Node version the problem was fixed. My errors looked like this:

TypeError: text.matchAll(...) is not a function or its return value is not iterable

If that was not the issue, could you please send the entire error log? You can just copy/paste the text.

[gelilaa]

@AlinaTaoRao please check this pull request for fixing your error

What went less well?

• dev strategy-how to divide branches?

  • each page a branch? then how can 2 person collaborate to develop one page?

You are exactly right. one page is far too big to be one branch. The whole idea of Agile development is to deliver work in small, but consumable, increments.

• or each issue a branch(that will be too much branches)?

I have made a simple example workflow to help you understand what yours should look like. Your branch should contain a small amount of work that your team can review and merge. the smaller the branch work the easier to review and avoid conflicts

• design (Figma: from the very beginning)

You will be exploring Figma in the next module UX/UI as well. So no rush to understand everything but it is good to start now.

[AlinaTaoRao]

@arnochauveau Thanks for your advice. It worked. I upgraded my node.js form v14.17.6 to v16.13.0. The npm spell-check problem disappear.

[AlinaTaoRao]

@gelilaa Thanks for your feedback. I tried change the spell-check in package.json to "spell-check": "cspell \"./**\"", but it worked not well for me. I upgraded my node.js. There is no error any more . The example workflow is a very good. It solved my problem. 👍

[AlinaTaoRao]

Week 3

• [x] I have pushed my progress to my fork of exercises repo: hyf-group3

Check-In

I Need Help With:

What went well?

• HTML and CSS

  What went less well?

Lessons Learned

Read the clue in details and be patient. Try to fix lint problems.

Sunday Prep Work