Agile Project Management with Scrum

1. What is Scrum?
 There are many approaches in Agile such as Extreme Programming (XP), Crystal, Feature Driven
Development, DSDM Atern which adhere to the Agile Manifesto and its associated principles and
 Scrum is one of many agile approaches to product development which use the iterative and
incremental product delivery that allow feedback and collaborative decision making.
 The project begins with a clear vision from business and a set of product features in order of
importance.
 Product backlog contains the product features which is maintained by the customer or customer
representative referred to as the Product Owner.
Topic 3: Agile Project Management with Scrum

2. What is Scrum?
 Iteration or sprint(also called as timebox), is the set amount of time that the team has to
complete the features selected.
 Sprints are completed within 1-4 weeks in length, and that length is maintained throughout the
life of the project.
 Each sprint contains the tasks and features that have been selected from the product backlog and
this is referred as sprint backlog.
 Development team commit to sprint backlog and the task work begins. During this time in the
sprint, the team is allowed to focus on meeting the sprint goal.
Topic 3: Agile Project Management with Scrum

3. What is Scrum?
 Although the product backlog can be changed in preparation for the next sprint but no changes
to the sprint backlog are allowed.
 During the sprint, the team checks in daily with each other in the form of a 15-minute meeting
known as a scrum meeting.
 Each member reports on what they did yesterday, what they plan to do today, and what is getting
in their way.
 At the end of the sprint, the team demonstrate the task that have been completed to the
stakeholders and gathers feedback that will affect what they work on in the next sprint.
 Retrospective sprint meeting will be held to learn how to improve. This meeting is critical, as its
focus is on the three pillars of Scrum: transparency, inspection, and adaptation.
Topic 3: Agile Project Management with Scrum

4. Scrum Framework
Planning
Design
Testing
Release
Sprint
Product
Backlog
Sprint
Backlog
Final
Product
Topic 3: Agile Project Management with Scrum
1-4 Weeks

5. EPIC
Feature
Story Story
Task Task Task Task
Define
Business
needs
Define the
customer
needs
Define the
solutions
Higher level requirement
from customer
Smaller
requirement
• Developer review
• Estimate the story
• Perform the Testing
Epic, Story & Task
Topic 3: Agile Project Management with Scrum

6. Epic, Story & Task
 Epics is large product that can be broken down into a number of smaller tasks which are called
stories.
 Stories is also referred as user stories are short requirements from the perspective of an end
user. Stories are created throughout product development, more so leading up to iteration
planning and also during higher level product road mapping.
 Tasks are decomposed parts of a story. Tasks are usually defined by the people doing the work
(developers, QA, etc), whereas stories and epics are generally created by the customer or the
product owner representing the customer.
Topic 3: Agile Project Management with Scrum

7.  Product Owner : Responsible for getting the requirements from the customers.
• Define the features of the product
• Decide the release date and content
• Prioritize features according to the market value
• Adjust features and priority every iteration as needed
• Accept or reject work results.
 Scrum Master : Is a facilitator for an agile development team and enable close cooperation
across all functions.
 Scrum Team: Developers and QA – work on delivering the products.
Agile Roles
Topic 3: Agile Project Management with Scrum

8. The Agile Process Flow
 Concept - Projects are envisioned and prioritized
 Inception - Team members are identified, funding is put in place, and initial environments and
requirements are discussed
 Iteration/Construction - The development team works to deliver working software based on
iteration requirements and feedback
 Release - QA (Quality Assurance) testing, internal and external training, documentation
development, and final release of the iteration into production
 Production - Ongoing support of the software
 Retirement - End-of-life activities, including customer notification and migration
 This view presents the full Agile lifecycle model within the enterprise. In any enterprise there
may be projects operating simultaneously, multiple sprints/iterations being logged on different
product lines, and a variety of customers, both external and internal, with a range of business
needs.
Topic 3: Agile Project Management with Scrum

9. The Agile Iteration Workflow
 The Agile software development lifecycle is an iterative process and each iteration results in the
next piece of the software development puzzle such as working software and supporting
elements, documentation for use by customers - until the final product is complete.
 Each iteration is usually two to four weeks in length and has a fixed completion time. Due to its
time-bound nature, the iteration process is methodical, and the scope of each iteration is only
as broad as the allotted time allows.
 Multiple iterations will take place during the Agile software development lifecycle and each
follows its own workflow. During an iteration, it is important that the customers and business
stakeholders provide feedback to ensure that the features meet their needs.
Topic 3: Agile Project Management with Scrum

10. The Agile Iteration Workflow
A typical iteration process flow can be visualized as follows:
•Requirements - Define the requirements for the iteration based on the product backlog, sprint
backlog, customer and stakeholder feedback
•Development - Design and develop software based on defined requirements
•Testing - QA (Quality Assurance) testing, internal and external training, documentation
development
•Delivery - Integrate and deliver the working iteration into production
•Feedback - Accept customer and stakeholder feedback and work it into the requirements of the
next iteration
Topic 3: Agile Project Management with Scrum

11. Agile Project Management is adopted to shorten the development cycles and
increase the frequency of project releases
6 steps in Agile Project Management Methodology
Project Planning Roadmap Release Planning
Sprint Planning Daily Meeting Sprint Review &
Retrospective
Overview of Agile process
Topic 3: Agile Project Management with Scrum

12. Project Planning is about understanding the end goal and value
of that project. Scope is developed and the work is estimated by
breaking it into sprints or iterations
A roadmap is a list of all features that the final product should
have. It acts as a plan of action on how a project will evolve.
A plan is made for all feature releases and this plan is revisited at
the beginning of each sprint. Agile project methodology uses
shorter development cycles or sprints, with features released at
the end of each cycle.
Topic 3: Agile Project Management with Scrum

13. Sprint Planning ensures that each member has an assigned task
before sprint begins. Stakeholder plans what is to accomplish in
that sprint and that workload is evenly shared among the team.
Daily meetings help the team in accomplishing their daily tasks in
an efficient way. Each team member tells what they have
accomplished in the previous day and what is their task today.
Sprint review and retrospective helps the team to inspect itself
and plan to make improvement in the coming sprints. Sprint
retrospective takes place after the sprint review and before the
next sprint.
Topic 3: Agile Project Management with Scrum

14. Agile is a combination of iterative and incremental process models with focus on process adaptability
and customer satisfaction by rapid delivery of working software product.
Agile Methods break the product into small incremental builds. These builds are provided in
iterations. Each iteration typically lasts from about one to three weeks.
Every iteration involves cross functional teams working simultaneously on various areas like −
 Planning
 Requirements Analysis
 Design
 Coding
 Unit Testing and
 Acceptance Testing.
At the end of the iteration, a working product is displayed to the customer and important
stakeholders.
Agile Development Cycle
Topic 3: Agile Project Management with Scrum

15. Product Backlog
• Prepared by product owner which contain requirements from the
customers
• Product owner will prioritize the stories
1. Release Planning: All the team decide how many sprints required and each sprint how
many stories should develop and test.
2. Sprint Planning: Decide what are the stories to develop and tests, the time required and
different tasks of developer and tester need to perform.
2-3 weeks
Sprint 1
2-3 weeks
Sprint 2
2-3 weeks
Sprint 3
Sprint Backlog
• The sprint backlog consists of product backlog items that the team
agreed with their product owner to include during sprint planning.
• The team owns the sprint backlog and can determine whether new items
are added or existing items are removed.
Agile Development Cycle
Topic 3: Agile Project Management with Scrum