Professional Documents
Culture Documents
Agile Framework
Learning Objectives
At the conclusion of this lesson, students will be able to:
Explain the Agile mindset
Describe situations where Agile best fits
List the benefits of using Agile
Know the origin/history of Agile
Demonstrate an understanding of the Agile Manifesto, Values,
Principles and Practices
Compare traditional vs. Agile
What is Agile?
Methodology? No
Framework? No Discipline Design…
Another Fad
Iterative No Planning!
No
Documentati
on ! Process? …Silver
Approach? Bullet
Definition
Agile is a an approach of
building products or services by EMPOWERING and
TRUSTING people, acknowledging
CHANGE AS NORM, and promoting
CONSTANT FEEDBACK.
Definition
Doing Agile……
• Time-boxing • Limit Work in Progress (WIP) • Pair Programming
• Retrospective • Avoid Waste • Face to Face Conversation
• Spike Solution • Short Iterations • Osmotic Communication
• Planning Poker • Sprint Goals • Test Driven Development (TDD)
• Backlog Prioritization • Servant Leader • Velocity
• Progress Elaboration • Self -organization • Unit Testing
MANY AGILE • Minimal marketable Features • Team Agreements • Test First Development
PRACTICES • Personas • Release Goals • Technical Debt
• Story Mapping • Release Plan • Task board
• User Stories • Project Chartering • Swarming
• Product Backlog • Quality Assurance • Regression Test
• Visualize Workflow • Refactoring • Minimum Viable Product
• Wireframe • Relative Sizing • Last Responsible Moment (LRM)
• Daily Stand-up • Product Vision • ……..
Agile is…
No precise definition, rather a set of principles & practices based
on the Agile Manifesto
Disciplined project management approach
Business & delivery focus, welcoming change
Agile is a general concept, Scrum and XP are specific
implementations of Agile
Incremental framework, frequent delivery & continuous
feedback loops
Empirical process - frequent inspect and adapt cycles that
minimize waste
Agile is…(continued)
Accommodate rapid product changes
Frequent releases in short development cycles (iteration, time-
boxing etc.)
Minimum requirement/specification upfront, and test
documentation (if at all)
Self-organizing, self-managing, cross-functional teams that make
and meet commitments
Engineering practices that rapidly delivery high quality software
What Agile isn’t
Agile isn’t traditional methods
No big upfront design - BUFD
Not an ad-hoc approach
Isn't unplanned
Isn’t chaos
Isn’t unpredictable
Project Noise and Method Selection
Unknown
Requirement
Known
Known/Certain Unknown/Uncertain
Technology
Why Agile?
Better align
Reduce risk Improve team morale
IT/Business
James Jim Andrew Hunt Ron Jeffries Jon Kern Brian Marick
Grenning Highsmith
Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas
Agile Values
Individuals & interactions over Processes & tools
Comprehensive
Working software over
documentation
Design
Coding
Time
Integration
Testing
Deployment
Operations and
Maintenance
Final Software Out
Agile Incremental Delivery
Product Product Product
Increments Increments Increments
Higher
Priority
Velocity
Lower
Priority
1 2 3 4
Time Time
Value Delivery
Risk of Failure
Sample Project Status Reporting
TRADITIONAL AGILE
Iteration n
Feasibility Initiation Release Planning Iteration 3 Close Out
Iteration 2
Higher Epic Theme Iteration 0 Iteration 1
Priority
Stories
• Testing Agreement
NPV, IRR, ROI Project Lower • Team Environment
Charter Priority Stories • Architecture approach
Product • Dependencies
Backlog • Risks
Iteration Daily stand-up, Development,
Project Visioning Planning Testing, deployment, etc.
Review Retrospective
X
L
M L
S Increment
Next Iteration
High level estimating
Release Plan
Business Case with using affinity
Go back to Release Planning for Release
High level Estimates another release, or if final release,
go to project closeout
Product Roadmap Iteration
Backlog Backlog To Do In Progress Done
A. Velocity.
B. Team Satisfaction.
C. Working software.
D. Customer satisfaction.
Test Your Knowledge
Sara is assigned as a Scrum Master to the newly launched agile team. She
is being asked to provide the list of metrics to measure the progress.
Which metric will she provide as a primary measure of progress?
A. Velocity.
B. Team Satisfaction.
C. Working software.
D. Customer satisfaction.
Test Your Knowledge
Which of the following values is not mentioned in the Agile Manifesto?
A. Integrity.
B. Working Software.
C. Customer Collaboration.
D. Respond to Change.
Test Your Knowledge
Which of the following values is not mentioned in the Agile Manifesto?
A. Integrity.
B. Working Software.
C. Customer Collaboration.
D. Respond to Change.
Test Your Knowledge
Of the following choices, which one is a key reason to adopt an Agile
Methodology
1. Abstracted from Shuh, Peter (2005). Integrating Agile Development in the Real World
2. How sustainable is your agile transformation to sustainable organizational agility, Ahmed Sidky
3. Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software
Development with Scrum by Ken Schwaber and Mike Beedle
4. 7th Annual state of Agile versionone® Agile made easier development survey
5. The Agile impact report, Rallydev
6. Iterative and incremental development by Craig Larman, victor Basili
7. What’s the big fuss about Agile? by Ahmed Sidky
8. Manifesto for Agile Software Development
9. Principles behind the Agile Manifesto
All registered and unregistered trademarks (service marks, brands, icons, copyrights etc.) mentioned
on this course are the property of their respective owners.
Content that references these trademarks is not sponsored by, endorsed by, or affiliated with the
respective trademark owners. PMI-ACP®, PMBOK®, PMI®, and PMP® are either marks or registered
marks of the Project Management Institute, Inc.
www.ceolevel.com