Ashenafi: Agile development, 3 weeks

[ashenafykebede]

Study Plan

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

• [x] Class Recordings

  Collaborating 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.
• [ ] During development you communicate any changes in your personal situation that will impact the group.
• [x] When the project is finished your group can write a retrospective including concrete steps to make sure the next project goes smoother.

Planning

• [x] 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.
• [x] 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
• [x] You can work together to write a development strategy for must-have user stories.
• [x] You can work together to convert a development strategy into issues on a project board organized with labels and milestones.

Developing

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

[ashenafykebede]

Check-In [Week 1]

Exercise repository ( week 1)

What went well?

• My experience on how to use GitHub is getting better and better
• Collaborating with teams to build a project
• Creating exercise repo
  • setting up access management,
  • adding group members to the group repo,
  • setting up project board,
  • turn on discussions,
  • setting up live URL,
  • adding rules for code review for PRs, etc of the exercise repo which is generated from a template repo .
• Creating group issue in the class repository.
• Creating pull request
• Reviewing PRS
• Able to write a code that passes all the checks
• Every group member is so motivated to plan and collaborate on the multi-page website development

What went less well?

• As usual ,team time availability is so diverse to set up a meeting that all members can participate.
• When I run npm run format the code gets formatted but failed to pass npm run lint:css . I should edit manually the markdown file to pass linting. Of course the formatting will mess up again. In fact, this happens when you have a longer line and a table with many columns.

I need help with

npm run format and npm run lint:css

Lessons learned

• Agile development gives you the chance to start from the simplest design and develop into a complex target by including a user feedback. This paves the room for improvement before it is to late.

Preparation for Sunday class

• I am reading on some of the suggested study materials for the upcoming chapter

[colevandersWands]

When I run npm run format the code gets formatted but failed to pass npm run lint:css . I should edit manually the markdown file to pass linting. Of course the formatting will mess up again. In fact, this happens when you have a longer line and a table with many columns.

🤔 @ashenafykebede, this shouldn't happen. Can you send me a link to the branch where you're having this trouble? I can clone to debug it then update the template

[ashenafykebede]

Dear @colevandersWands

Many of the branches has this problem after the table grew bigger. We can take this branch where I specifically noticed the issue. Especially, the communication.md file as it contains a table with many columns.

To add a bit more about the problem, the npm run format makes the table so good in the markdown file but the table now expands more than 80 lines per row which npm run lint:md fails to pass.

Thank you so much in advance

[colevandersWands]

To add a bit more about the problem, the npm run format makes the table so good in the markdown file but the table now expands more than 80 lines per row which npm run lint:md fails to pass.

thanks for the extra details. I think this is an easy fix in the linting configurations, you can tell it not to check the line-length for tables. Checking now to be sure

[colevandersWands]

🤕 oops, I meant to send a PR with this fix but accidentally merged to your main because I forgot I have write access. anyway, this should fix it!

[ashenafykebede]

Check-In [Week 2]

Exercise repository ( week 1)

What went well?

• It was a nice week. I am working on the deliverables with my group members

What went less well?

• Nothing

I need help with

-

Lessons learned

• Working as a group is fun and adventure. A lot of brainstorming, collaborative work, get to know more about each other, different views, different availabilities etc

Preparation for Sunday class

• Working on the group project especially on planning.

[ashenafykebede]

Check-In [Week 3]

Exercise repository ( week 3)

What went well?

• The communication and collaboration became much better than the previous weeks.
• There was a clear idea and agreement of what we are going to build as a team.

What went less well?

• Nothing

I need help with

• Nothing

Lessons learned

-We were able to create a nice homepage by taking feedback and adding modifications to the proposed website design. This is the agile way!

Preparation for Sunday class

• Reading study materials