References:
- Lei, H., Ganjeizadeh, F., Jayachandran, P. K., and Ozcan, P. 2017. A statistical analysis of the effects of Scrum and Kanban on software development projects. Robotics and Computer-Integrated Manufacturing, 43, 59-67.
- Dursun, M. Goker, N., and Mutlu, H. 2019. An Intuitionistic Fuzzy Decision Aid Approach to Analyzing Performance Indicators of Waterfall Project Management Framework. ICBIM ‘19: Proceedings of the 3rd International Conference on Business and Information Management, 195-198.
- Pace, M. 2019. A Correlational Study on Project Management Methodology and Project Success. Journal of Engineering, Project, and Production Management, Vol. 9, Issue. 2, 56-65.
- Mani, D. 2020. Agile Methodology in Product Management. The Innovation.
- Cervone, H. 2011. Understanding agile project management methods using Scrum. OCLC Systems & Services, Vol. 27, Issue. 1, 18-22.
- Cobb, C. D. (2011). Making Sense of Agile Project Management: Balancing Control and Agility. John Wiley & Sons, Inc. New York, NY.
The Agile framework refers to alignment, where alignment involves the developers and stakeholders to collaborate with one another to align the desired product with the customer needs.
The Scrum framework is characterized by overlapping phases of development, such as, analysis, design, implementation, and testing.
- Scrum is a strategy that organizes the team to reach a common goal, creating a product.
- To achieve success with Scrums, the Sprint concept is a great tool to utilize.
Sprints are defined as real-time events, with the primarily focus on fixed-length iterations.
- Generally, lasts one to two weeks and it allows the team to initiate software on timed intervals.
- It is essential that the team and stakeholders (end-users) meet to coordinate the next steps.
Sprint Components and Logistics:
- Product Owner & Developers work collaboratively as a Scrum Team.
- Scrum Team must be committed throughout the timed and scheduled intervals.
- Several weeks to complete.
Figure 1 – Timing Image
Sprint Component Definitions:
- Product Owner – Business representative dedicated to the team.
- Scrum Master – Dedicated role that protects team and helps them improve.
- Sprint Leader – Dedicated technical/functional role that drives the Sprints.
Figure 2 – Sprint Team Leadership Image
Sprint Team Member Responsibilities:
Product Owner Responsibilities:
- Business unit representative.
- Reviewer/approver for team’s work.
- Ensures stakeholders values are met.
- Interacts with stakeholders (end-users).
- Oversees product vision.
Sprint Leader & Scrum Master Responsibilities:
- Oversees team's functionality.
- Reviewer/approver for team’s pace.
- Liaison for team.
- Ensures that roadblocks are removed.
- Ensures team accountability to product owner.
Create Sprint User Story:
- Functional User Story – Describes the end goal from end-user’s perspective.
- Non-functional Story – Describes how to accomplish the user story from the developer’s perspective.
 |
 |
| Figure 3 – User Story Image |
Figure 4 – User Story Template Image |
Understand Functional and Non-functional Sprint User Story:
 |
 |
| Figure 5 – Functional User Story Example Image |
Figure 6 – Non-functional Story Example Image |
Obtain Acceptance for Sprint User Story:
Figure 7 – Acceptance Criteria Example Image
Create Task Board (Cardwall) for Sprint User Stories:
 |
 |
| Figure 8 – Task Board Image |
Figure 9 – Task Board Example Image |
4-benchmarks that provide structure to each sprint:
1. Sprint planning: This step involves the stakeholder to present the top items on the backlog to the team in a sprint planning meeting. The team then chooses which work they can complete during the sprint and moves the work from the product backlog to the sprint backlog, which is a list of tasks to complete during the sprint.
Figure 10 – Sprint Planning Meeting Image
Create Themes and Roadmap (schedule) from User Story:
 |
 |
| Figure 11 – Themes Example Image |
Figure 12– Roadmap Image |
Develop Product from Theme (example from Profile Theme):
Figure 13 – Profile Theme Example Image
Develop Sprint Task Hours (how long) from User Story:
Figure 14 – Sprint Task Hours Example Image
Obtain Sprint Commitment Level:
Figure 15 – Obtain Sprint Commitment Image
2. Daily Stand-Up: This step involves coordinating 15-minute stand-up meetings where each team member talks about their goals and any issues that have come up. The Daily Scrum happens every day during the sprint and helps keep the team on track.
Figure 18 – Standup Discussion Questions Image
3. Sprint Demo: This step involves coordinating meetings at the end of each sprint. During these meetings the team presents the work they have completed at a sprint review meeting. This meeting should feature a live demonstration, not a report or a PowerPoint presentation.
Figure 19 – Sprint Review Image
Figure 20 – Demo Communication Image
Figure 21 – Demo Relationship Image
Figure 22 – Demo Progress Image
4. Sprint Retrospective: This step involves coordinating meetings at the end of each sprint, where the team reflects on how well Scrum is working for them and talks about any changes that need to be made in the next sprint.
Figure 23 – Retrospective Image
Figure 24 – Retrospective Agenda Image