Let's do Scrum!

[KohmeiK]

1. Getting Started

• Define your first Scrum Team
• Define your Sprint length
• Appoint a Scrum Master
• Appoint the Product Owner
• Create the Initial Product Backlog and Functional Model #13

2. First Sprint Planning Meeting

• Define a sprint goal
• Move stories from your Product Backlog to Sprint (Add / update T-shirt sizing and prioritize tasks)
• Assign teams to stories
• Set Dependencies between tasks
• Setup Burn-down chart to track velocity

3. First Daily Scrum

• Have everyone answer the following questions:
  • What have I done since the last meeting?
  • What do I plan to complete before the next meeting
  • What problems am I likely to face?
  • Update Scrum Board
• Discuss inter-team task dependencies
• Show burn-down chart to see if deadline will be met

4. First Sprint Retrospective

• Have each team member identify specific things that the team should:
  • Start doing
  • Stop doing
  • Continue doing
• Refine / Vote on the improvement ideas generated and apply them to the next sprint

WARNING! Even though Scrum is simple to understand, it is difficult to master. Some people on the team will love it and some people will hate it. This is perfectly normal and you should encourage people on the team to give it a proper try before they give up. If an individual ends up giving up, then remove them from the team and let another one step in. This also means that the person that is taken off the team no longer should work on the project.

Remember that Scrum projects tend to be hard to predict, from timelines to budgets. Without a concrete plan and complete requirement set, everything remains a bit vague. So much so that agile projects can easily go off the rails when project managers are unsure about the outcomes they want to achieve.
(https://www.forecast.app/blog/implementation-of-scrum-7-steps)