0% found this document useful (0 votes)
41 views13 pages

Agile Framework

The document outlines the Agile framework, specifically comparing Waterfall and Scrum methodologies, emphasizing Scrum's iterative and flexible nature. It details the process of writing effective user stories, defining 'done', and the various touchpoints in Scrum including discovery, planning, daily standups, reviews, and retrospectives. Additionally, it sets expectations and team roles for each phase, highlighting the importance of collaboration and continuous feedback throughout the project lifecycle.

Uploaded by

ram
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views13 pages

Agile Framework

The document outlines the Agile framework, specifically comparing Waterfall and Scrum methodologies, emphasizing Scrum's iterative and flexible nature. It details the process of writing effective user stories, defining 'done', and the various touchpoints in Scrum including discovery, planning, daily standups, reviews, and retrospectives. Additionally, it sets expectations and team roles for each phase, highlighting the importance of collaboration and continuous feedback throughout the project lifecycle.

Uploaded by

ram
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

AGILE FRAMEWORK

WHAT CAN GO WRONG?


in delivering the project successfully Left blank intentionally for discussion with team
WATERFALL vs SCRUM

o Scrum is iterative and incremental


o Each Iteration results in finished
product which is potentially
releasable.
o Scrum is flexible and embraces
changes late in the project stages
WRITING GOOD STORIES
Independent - as much as possible
Negotiable - not a contract, a conversation
Valuable - High Value, High Priority
Estimable - Properly sized
Small - Done within 3-4 days
Testable - Clear acceptance criteria
DEFINITION OF DONE
Left blank intentionally for discussion with team

o What is our DoD of Story


o What is our DoD of Iteration
o What is our DoD of Release
Multiple Touch-Points in
SCRUM

Discovery

Release Planning

Backlog Prioritization

Iteration Planning

Daily Standups

Iteration Review

Iteration Retrospective
EXPECTATIONS
● Identify the roadmap of the project
● Milestones of the project
● Feasibility and expectation setting with Customer

Scope and all of the features may not get freezed though

TEAM ROLE
DISCOVERY
● Participate in discovery
● Identify risks/unknowns and carry out PoCs for same
● Sort out project prerequisites

FREQUENCY & DURATION


● Once
● 2 days-2 weeks (project specific)
EXPECTATIONS
● A tentative estimate of the stories in backlog
● Rebaseline release dates of milestones
● Rebaseline features in releases

TEAM ROLE
● PO will bring well written user stories for release planning
RELEASE PLANNING
● Team must provide best estimates as per current understanding

FREQUENCY & DURATION


● At least once every two iterations.
● 2 Hours at the beginning of the project
● 1 Hour (must reduce as we move further in project)
EXPECTATIONS
● Theme of the iteration
● Pick stories which will be DONE in the iteration
● Team members to understand and articulate the technical approach
and acceptance criteria of the stories
Do we need an intermediate meeting for better understanding and estimates?
Does doing planning on sheets helps team focusing on stories rather than filling up tool with right
ITERATION PLANNING data?

TEAM ROLE
● PO to bring prioritized, well defined stories for planning
● Team members to bring their capacity plan for iteration

FREQUENCY & DURATION


● Start of the iteration (I would prefer a morning meeting, need comments and feedback)
● 2 Hours
EXPECTATIONS
● Prioritize Backlog for upto next two iterations as least.
○ Upcoming iteration stories must be ready by mid of current
iteration. Dependencies must be sorted as well.
○ Upcoming + 1 iteration stories must be identified with customer
and should be ready to define acceptance criteria and any
dependencies
BACKLOG PRIORITIZATION
TEAM ROLE
● PO, TA and other relevant team members must be included.

FREQUENCY & DURATION


● Once every iteration, ideally mid of the iteration
● 1-2 hours. Will run couple of these and then we can decide the duration
EXPECTATIONS
● To understand if we are on the right course with right speed to
complete iteration
● Bubble up dependencies

TEAM ROLE
● Run daily standups

DAILY STANDUPS ○ One person from team will run standup. Whoever is joining last
○ Check that timesheet is filled by team before standup
○ Take notes of stand up and share. Highlight dependencies.
● Answer
○ What was done yesterday
○ What will be done today
○ Dependencies

FREQUENCY & DURATION


● Daily 15 min
EXPECTATIONS
● Get early feedback on features completed
Ideally customer should join as well

TEAM ROLE
● Prepare for demo, setup demo environment.
● Deploy completed stories on demo environment
ITERATION REVIEW
● Each team member to demo their respective stories
● PO to take notes on feedback and incorporate in release plan

FREQUENCY & DURATION


● Last day of iteration
● 1-2 hours
EXPECTATIONS
● Identify areas where team needs to improve
● Define action items, owners, dates
● Reflect on previous action items and areas identified

TEAM ROLE
● Bring their observations from iteration. Answer
ITERATION RETROSPECTIVE
○ What are we doing good
○ What we need to start
○ What we need to stop

FREQUENCY & DURATION


● Last day of iteration
● 1 Hour

You might also like