Scrum agile development basics summary
Scrum: What? Why? How?
Scrum as an agile project management allows a team to adopt to changes in real-time by delivering milestones as small pieces. Traditional Waterfall method can be useful in certain projects like building construction but for projects like software development it may not be so fruitful as a result agile methods have come to practice.
How Agile is different?
- Agile asks business partners to work with the team throughout the project where this ongoing interaction will result of delivering the product they really need.
- In agile instead of just using mile-stones we measure success using completed software.
- Agile allows teams to self-organize
- Fail Fast: agile methodology makes the project to fail fast if it is going to! So, you don’t need to wait for a long time and see the product is not aligned with your business requirements.
How Scrum works?
- The Product Owner preauthorizes a backlog of work
- Every two-four week looks at the backlog and decides what work can be done next
- They work, develop and test the solution for the next two-four weeks
- Team demonstrates its completed work to the Product Owner and stakeholders
- Team reflects how it can be improved
Product Owner is a full-time expert who acts as a business representative dedicated to the team to review the team’s work and ensure highest value delivery, interacts with stakeholders and maintains product vision.
Scrum Master acts as spokesperson of the team and helps the team to resolve day to day issues and counter balance ongoing requirement changes and improve efficiency.
Standup Scrum (Stand-up Meeting) is a day to day team meet usually up to 15 minutes to discuss progress and issues.
Retrospective is a meeting focusing on the team to reflect ideas on how to improve.
MVP is a product which is ready enough to present and get user feed back
Product Vision is written by the PO and serves as a guide for the team to get the general idea of what the product will be. The vision then will be decomposed to Themes and Features and finally User Stories.
User Story is a detailed, valuable chunk of work that a team can quickly deliver usually wrote by the PO and added to the backlog.
A good user story is Independent Negotiable Valuable Estimable Small Testable