Master Four Ceremonies to deliver Agile projects better

®
1 | 2/18/2019 © Copyright 2006-2018 Inflectra Corporation
Master Four Ceremonies to
deliver Agile projects better
Journey into Agile with Inflectra
By: Sriram Rajagopalan
We will be starting the webinar shortly, please stand by…
All phones will be automatically on mute until the Q&A.
Webinar Starts at 2:00 PM Eastern Time Zone

®
Meet the Speaker
Dr. Sriram Rajagopalan
Education
Work
Experience
Training &
Certification
Teaching
Experience
PhD, MBA, MS, BE
PfMP, PgMP, PMP, SP,
RMP, ACP, CSM, CSPO,
ACC, CSD, SCT, CSOXP,
SSBB, Instructional
Designer, Speaker,
Writer, and Author
Software Engineer,
Team Leader,
Business Analyst,
Project Manager,
Scrum Master, Agile
Coach, Director,
Vice President
Several
Colleges in the
US, India, &
Vietnam

®
Introduction
 Today’s webinar is part of the 5-part series on “Journey
into Agile with Inflectra”
 Each webinar is 1-hour long. We will reserve time at the end
for questions
 The webinars introduce the concept using a tool
 There is some expectation on your part to setup access
with the SpiraTeam®
 The completion certificate is based on specific requirements
and passing a certification quiz

®
Agile By Inflectra Certificate Course
Start
Register for Webinar
Attend
View Archive when
available
Experiment with SpiraTeam
Pass Quiz
Do for all 5 webinars
End http://www.inflectra.com/Ideas/Entry/agile-by-inflectra-faqs-certificate-course-771.aspx
No
Yes

®
Journey into Agile with Inflectra
Five Principles
to Application
Lifecycle
Management
Master Four
Ceremonies to
deliver Agile
projects better
Master Five
Essentials to
managing your
requirements
Cutting the
Costs and
improving the
Quality
Excellence
through
Reporting in
Agile Projects

®
Understanding Context
Strategy
Portfolio
Product
Release
Iteration
Daily
Measurable Organizational Value
(MOV)
Minimum Viable Product
(MVP)
Minimally Marketable Feature
(MMF)

®
Agility is a “Change Mindset”
Extrinsic
Value
Intrinsic
Value
Team
Ownership
Constraints
Continuous Integration
Refactoring
Testing
Agile Documentation
Small Releases
Product Ownership
Agile Practices Agile Thinking

®
Getting Grounded – Agile Mindset
Focus on
Value
Small
Batch Size
Elimination
of Waste

®
Agile is a Framework of Frameworks
AgileLean
Kanban
Scrum
ScrumBan
XP DSDM
Crystal
TDD
FDD
AUP

®
Experience Speaks
Reduce
Time to
Market
Reduce
Cost to
Operations
Increase
Value to
Customer
Increase
Quality to
Product

®
Among many misinterpretations, one challenge is adapting change!

®
Agile Failure Patterns
Lack of
Strategic
Vision
Lack of Self-
Organization
Management
Culture
Appetite for
Failure
Inadequate
Transparency
Siloed
functional
teams

®
Four Agile Ceremonies
Iteration
Planning
Daily
Standup
Review Retrospective

®
Four Agile Ceremonies
90%
88%
85%
80%
Daily Standup Iteration Planning Retrospective Iteration Review
Ref.: State of Agile 2018 Survey

®
Iteration Planning
 Goal
 Team to select appropriate mix of value added stories
 About 4 hours for 2-week iteration
 Owners
 Product Owner, Scrum Master, Team
 Prerequisite
 Risk-Adjusted Prioritized Product Backlog; Backlog Grooming
 Result
 Prioritized list of stories
 Deliverable list of stories (Velocity/Commitment driven planning)

®
Some Reasons for Iteration Planning failure
 Challenges
 Adequate number of stories are not in a “Ready” state
 Requirements are not prioritized and aligned
 Teams are not cross-functional and self-organized
 Same person plays both the scrum master and product owner role
 Opportunities
 Transparency to Requirements in backlog
 Foster team collaboration to continuous grooming
 Bidirectional traceability to grooming test cases

®
Games helping Iteration Planning
Product Box Buy a Feature Prune the Tree

®
Daily Standup
 Goal
 Team to report on their progress
 Team to get feedback and raise impediments
 Owners
 Team, Scrum Master, Product Owner
 Prerequisite
 Sprint Commitments in Sprint Backlog
 Product Owner Availability
 Result
 Addressing Impediments to reach “done” status
 Avoiding micromanagement
 Eliminating unnecessary interruptions

®
Daily Standup
 Characteristics
 Timeboxed to 15 min (Maintain focus)
 Answers three basic questions
 What did you do yesterday?
 What are you doing today?
 What are the impediments?
 (Optional) What is coming to another team’s way?

®
Reasons for Daily Standup Failure
 Challenges
 Unavailable Product Owner
 Same individual playing the Product Owner & Scrum Master roles
 Treating Daily Sprint as a Status Check meeting
 Team members not self-organized to report progress
 Early and Unnecessary visitors requesting demos
 Physical Environment unfriendly for daily sprint
 Time-zone and Technology challenges
 Opportunities
 Several reporting widgets providing updates
 Auditable comment features for virtual team to report progress
 No tool, however, can and should replace Daily Sprint

®
Games helping Daily Standup
Valuable Paper
Airplane
Matchup Canvas Daily Scrum
Game

®
Review
 Goal
 Team to report progress on ‘done’ and ‘not done’ (product focus)
 Team to inspect and adapt
 2 hours for 2-week sprint
 Owners
 Product Owner, Team, Scrum Master
 Additional Stakeholders
 Prerequisite
 Product Owner Availability
 Good state of Product Backlog
 Product Owner collaboration with other stakeholders
 Result
 Product Owner accepting ‘done’ stories
 Stakeholder alignment on product backlog (specific to market demand)
 Criteria for subsequent iterations

®
Review Ceremony: Challenges & Opportunities
 Challenges
 It is like “Show and Tell”
 It is not just a demo
 It is an opportunity to inspect and adapt
 Product Owner not owning the Product Backlog
 Not enough continuous grooming of stories and prioritization
 Opportunities
 Increasing transparency
 Augment accountability

®
Games helping Review
Speed Boat Pass on
Perfection
Feedback Game

®
Retrospective
 Goal
 Team to periodically review what’s working and not working (process focus)
 Team to inspect and adapt
 1-2 hours for 2-week sprint
 Owners
 Product Owner, Team, Scrum Master
 Customers and other Stakeholders
 Prerequisite
 Product Owner and Scrum Master Availability
 Focus on the challenges and not the member
 Mandatory and non-negotiable
 Result
 Identifying owners to address challenges
 Incorporate “Start Doing”, “Stop Doing” and “Continue Doing” improvements

®
Retrospective Challenges and Opportunities
 Challenges
 It is NOT a “blame game”
 It is NOT a “documentation exercise”
 Opportunities
 Increasing transparency
 Augment accountability

®
Games for Review also helps Retrospective
Speed Boat Pass on
Perfection
Glad Sad Mad

®
Demo Time
 Let us explore specific areas on how SpiraTeam® supports
agile projects

®
Summary
All agile projects should uphold the four ceremonies
• Iteration/ Sprint Planning
• Daily Sprint
• Review
• Retrospective
Focus should be to improve “Transparency”, “Inspection”, and “Adaptability”
• Increase value to Customer
• Increase quality to Product
• Reduce time to Market
• Reduce cost to Operations

®
Q & A
 Please feel free to ask
questions
Course Administration
Ms. Thea Maisuradze
marketing@inflectra.com
Content
Dr. Sriram Rajagopalan
sriram@inflectra.com.

®
Next Steps
1. Take the post-webinar quiz (link in email)
2. Register for the 3rd webinar of the series!
Thank you for watching!

Master Four Ceremonies to deliver Agile projects better

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Master Four Ceremonies to deliver Agile projects better

Similar to Master Four Ceremonies to deliver Agile projects better (20)

More from Sriram Rajagopalan

More from Sriram Rajagopalan (14)

Recently uploaded

Recently uploaded (20)

Master Four Ceremonies to deliver Agile projects better

Editor's Notes