Agile Framework

Sample Courseware Contents

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 project management methods
 Identify high-level differences from one Agile method to another
 Being Agile……
1. Individuals and interactions over processes and tools 3. Customer collaboration over contract negotiation
4 AGILE VALUE 2. Working software over comprehensive documentation 4. Responding to change over following a plan

6. The most efficient and effective method of conveying

1. Our highest priority is to satisfy the customer through early
information to and within a development team is face-to-face
and continuous delivery of valuable software.
conversation.
2. Welcome changing requirements, even late in development.
7. Working software is the primary measure of progress.
Agile processes harness change for the customer's
8. Agile processes promote sustainable development. The sponsors,
competitive advantage.
developers, and users should be able to maintain a constant pace
3. Deliver working software frequently, from a couple of weeks
indefinitely.
12 AGILE to a couple of months, with a preference to the shorter
9. Continuous attention to technical excellence and good design
timescale.
PRINCIPLES 4. Business people and developers must work together daily
enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--
throughout the project.
is essential.
5. Build projects around motivated individuals. Give them the
11. The best architectures, requirements, and designs emerge from
environment and support they need, and trust them to get
self-organizing teams.
the job done.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.

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 • ……..
What’s Different?
Traditional Agile
Defined process: Control and Coordinated Empirical process: Inspect and Adapt
Work is organize around the team Team organize around work
Work is assigned or push to the team Work is store in queue and team pull the tasks
Plan all in advance Plan as you go
Work breakdown structure Feature breakdown structure
Functional specs User stories
Gantt chart Release plan
Status report Information radiators/deliver as you go
Learn at the end Learn every iteration
Follow the plan Adapt everything
Manage task Manage team
Conventional project team Self-organized project teams
Avoid change Embrace change
Prescriptive Adaptive
Multiple Level of Planning

Vision
Roadmap
Release
Iteration

Daily

Planning Onion
Factors in Backlog Prioritization
1 USER STORY
Dependencies 2 USER STORY Value
3 USER STORY
4 SPIKE
5 USER STORY
6 USER STORY
7 USER STORY
Risk Resources
8 DEFECT
9 USER STORY
10 SPIKE
11 USER STORY
12 USER STORY
Cost 13 USER STORY Knowledge
14 DEFECT
 Operating Model of Agile Team
Functional Teams Agile Teams
Project Manager
Business Analyst Coach/Facilitator
Testers/QA
Product Owner
Customer
Developer Cross
Support Product functional
Engineer Teams
Manager

• Team organized around the work

• Work is organized around the team • Empowered
• Tasks are assigned (most of the time by the PM) • Self organize / Self managed
• Functional silos • Team pulls the task from queue /backlog
• Cross functional
• Intensely collaborative
Activity: Sequence the Scrum Events
Sequence the Scrum Events
5 Minutes
Iteration 1 Iteration 2 Release
2 Weeks 2 Weeks

Retrospective 2 Retrospective 1 Daily Stand-up Release Planning

Sprint 2 Review Sprint 1 Review Sprint 1 Planning Product Backlog

Refinement
Sprint 2 Planning Product Backlog
Creation
Activity: Match the Definitions
Match the Definitions
10 Minutes
1 Product Development A The means to reach the Product Vision

2 Product Owner B what it takes to have a Product Backlog item done

3 Scrum Master C meeting to improve the work of the Scrum team

4 Customer D delivery of product increment(s) to the customer

5 Product Vision E the one defining the product
6 Product Increment F the ones getting frequent ROI and providing feedback
7 Sprint Backlog G the Sprint plan
8 Product Backlog H meeting to get feedback on the product
9 Definition of Done I meeting to plan the next day
10 Release J what is the overall need to be supplied
11 Sprint K the ones building the product
12 Sprint Planning L valuable slice of the product produced in a Sprint
13 Daily Scrum M meeting to plan the next Release
14 Sprint Review N the facilitator and Scrum process coach
15 Sprint Retrospective O the development cycle
16 Release Planning P meeting to plan the current Sprint
Test Driven Development (TDD)

1. Add a Test
In TDD, a programmer writes a test
before they write any code. The test
RED fails and the programmer writes just
enough code to make it pass. This cycle
is repeated on timelines of every few
REFACTOR GREEN minutes.

3. Make it clean
2. Make it work Test -> Code -> Refactor