Agile Project

ManagementMGMT-6061
Module 14

Project, Sprint Demo,

Course Review
Module 14

Learning Outcomes
• Evaluate and appraise a Sprint Demo
• Interation lengths
• Final word on User Stories

This slide presentation augments your Course and

Module Readings. Complete the module readings
before reading through this presentation.
The Sprint Review (Demo)
• Having made progress on a few sprints for your group
project, how would you demo the product from your
assignment at the end of each sprint?
• Each Sprint Review is an opportunity to improve the product,
without continuous feedback it’s easy to veer off course.
• The emphasis is on gathering feedback, not gaining “formal”
approval from the attendees.
Scaling up Scrum
• Would it be a good idea to stagger the Sprints..??
Scaling up Scrum
• Not a good idea…..

• Very difficult to show your end user/customer what you have completed. All of the teams
are never done meaning some teams are partway into their iteration.
Scaling up Scrum
• Synchronize your Sprints

• Have all iterations end within a two or three day

period.
Iteration Length
• What to consider:

• How often can product be shown (in potentially

shippable form) to users and customers.
• How often the team and its customer can adjust
project goals.
• How often progress can be measured.
Priorities
• Priorities should remain unchanged

• Once you have committed to user stories for the

Sprint don’t be distracted or feel you need to
change mid-sprint

• Start a new user story in the next Sprint

Iteration Length
• Uncertainty (high risk projects/user stories)

• The more uncertainty of any type the shorter the

iterations should be
Sprint Overhead
• If your Sprints have a lot of testing you may want
longer Sprints

• If your Sprints have complex user stories you may

want longer Sprints
Back End Loaded Sprints
• Avoid back end loaded sprints

• Work at a sustainable pace.!!

• “One of the main goals in selecting an iteration length

is finding one that encourages everyone to work at a
consistent pace throughout the iteration” (Cohn, 2021).
User Stories – the final work
• Anyone can write a user story
User Stories – the final work
• Anyone can write a user story

• When are they written.?? – anytime during the

project

• Written in plain language…. In the language of the

customer
User Stories – the final work
• They are not use cases

• A use case is a generalized description of a

set of interactions between the system and
one or more actors, where an actor is either
a user or another system (Cohn, 2021).
WOW
• wow
Reflection on Agile
• What are the top 3 biggest things that are different
between planned project management and Agile?
• Where is personal and team discipline required for
Agile?
• Why wouldn’t everyone be a “fit” on an Agile team?
Reflection on Agile
• What do you think about Scrum
development.????
Course Review for the Final Exam
• Review your readings and the presentation files for
the course, with the emphasis being on post mid-
term content
• Perform any review exercises or quizzes provided
End of Module
Parts of this document were sourced from:

Essential Scrum - A Practical Guide to the Most Popular Agile Process

Author: Kenneth S. Rubin
Publisher: Pearson Education, Inc