2. Welcome & Introductions
Play Scrapper Video

3. Traditional Agile Teams Teams Process Process Delivery Cycle:
Traditional vs Agile
-Review what the Traditional “Waterfall” project methodology. Discuss how the phases are distinct with document hand-offs, silos, independent development.
-Discuss how little input the stakeholders have after the requirements phase.
-Complication of Change Control process
Delivery Cycle:
4 to 6 months
Delivery Cycle:
2 to 4 weeks
Leader: Project Manager
Manages delivery of product
Leader: Scrum Master
Facilitates process & team dynamics

4. Shapes Game Fold the paper in half Draw a square
In the upper left hand corner draw a circle
At the top of the page draw a triangle
Draw a straight line on the left and right side of the square
Draw a rectangle in the square
Shapes Game
Pass out a blank piece of paper
Remind the team that if the drawing does not look exactly like the picture on slide 5 that it will not pass Stakeholder approval
Rules:
-Do not start drawing until the instructor gives the ok
-Read the requirements out loud
-allow the class 2 min. To illicit additional requirement
Done: I will know it when I see it

5. Shapes Game Reveal
How close did the class get?

6. Defining Agile Transformation

7. . Agile Manifesto Individuals & Interactions Over Processes & Tools
“We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals & Interactions Over Processes & Tools
Working Software Over Comprehensive Documentation
Customer Collaboration Over Contract Negotiation
Responding to Change Over Following a Plan
Review the Agile Manifesto.
Explain that we value the things on the left more than those on the right.
That does not mean we will not do the things on the right, but we will question the value, and do only what adds value.
“That is, while there is value in the items on the right, we value the items on the left more.” .

8. Agile Family Tree SCRUM Kanban Lean Six Sigma TDD
eXtreme Programming (XP)
Story: Defining Agile an Transformation
Agile Family Tree

9. Story: Defining Agile an Transformation

10. Paper Airplane Game Your own sub headline Rules Sprint 1
Time: 2 mintues
Each team will be building paper airplanes
Team:
1 designer; can only verbally describe the design, may not build or test
2 builders; can only build they can not test
2 testers; test and accept or reject paper airplane
Team Committment:
-30 seconds
Acceptance Criteria:
-Need to look like an airplane
-Need to fly 12 feet
-Fly relatively staight
Paper Airplanes Game
Review Rules:
Request that each team provide an estimate on how many paper airplanes they can complete in 2 min.
At the end: Write down the number of completed\accepted airplanes-did the airplanes meet the design proposed by the designer

11. What didn’t work and why?
Paper Airplane Restrospective
Your own sub headline
What Worked?
What didn’t work and why?
Paper Airplanes Game Retrospective
What should we try?

12. Paper Airplane Game Your own sub headline Rules Sprint 2
Time: 2 mintues
Each team will be building paper airplanes
Team:
Self Organized team; the team can define roles
Team Committment:
-30 seconds
Acceptance Criteria:
-Need to look like an airplane
-Need to fly 12 feet
-Fly relatively staight
Paper Airplanes Game
Review new rules:
Explain to the team that they can now implement any improvements that they would like to make the process.
Request that each team provide an estimate on how many paper airplanes they can complete in 2 min.
At the end: Write down the number of completed\accepted airplanes

13. What didn’t work and why?
Paper Airplane Retrospective 2
Your own sub headline
What Worked?
What didn’t work and why?
Paper Airplanes Game Retrospective 2
What should we try?

14. Traditional Agile Teams Teams Process Process Delivery Cycle:
Traditional vs Agile
Review the Agile process, compare\contrast to Traditional
Delivery Cycle:
4 to 6 months
Delivery Cycle:
2 to 4 weeks
Leader: Project Manager
Manages delivery of product
Leader: Scrum Master
Facilitates process & team dynamics

15. Scrum Team Release lan Business Vision Process Facilitator
Technical Vision
Process Facilitator
Agile in practice
Review the Leadership Triangle and Team
Review Roles
Review importance team removing Silos
‘Generalizing Specialists’

16. Scrum is named for a formation in rugby, which is used to get the ball moving after it has gone out of play.
Players mass together around the ball and with their heads down exert all their power and concentration to get the ball moving.
Scrum stuck because of the similarities between the game of rugby and the type of product development prescribed by Scrum.
Agile in practice
Where did Scrum gets its name; Rugby.
How is Scrum similar to Rugby

17. Scrum Ceremonies Sprint Planning Sprint Backlog (Tasks)3 5 8 2 13 1
Create UI (5 hrs)
Code, Unit test validation logic (3 hrs)
User Acceptance Testing (2 hrs)
Daily Scrum\Standup
What did I complete yesterday?
What am I working on today?
What implements are slowing me down?
Agile Ceremonies in practice
Review the following items
-Story Cards (Artifact)
-Story Tasks(Artifact)
-Product Backlog (Artifact)
-Sprint Planning (Ceremony)
-Daily Scrum\Standup (Ceremony) -3 Questions
-Sprint Review\Demo (Ceremony)
-Sprint Retrospective (Ceremony)
Sprint Review\Demo
Sprint Retrospective
Product Backlog

18. Scrum Artifacts Measurement! Burn-up Burn-down Velocity Trend
Agile Artifacts in practice
Review what an Artifact is and the various types that the team may encounter.
Review what Velocity is? What was the Velocity after Sprint 2 of the Airplane Game
Velocity Trend

19. Scrum Artifacts Product Backlog Agile in practice
Examples of Product Backlog
Product Backlog

20. To Do: Done: Underway: Pack Send Utilities Deposit Buy Boxes & Tape
Scrum: Moving Day
Denotes Impediment
To Do:
Underway:
Done:
Send Utilities Deposit
Pack
Scrum in practice
How do we keep track of the work?
Collaboration during Standup
-Review Impediments, who’s job is it to remove impediments (Scrum Master)
Buy Boxes & Tape
Call Movers

21. Collaboration Rooms! Story: Agile in practice
Copyright© Agile Transformation Inc

22. Agile Characteristics
Pairing
Daily Standup
Cross Functional Team
Self-Organizing
Agile in practice
More real-life pictures
Business/IS as One
Copyright© Agile Transformation Inc

23. Agile Key Terms “Backlog” “User Story” “Sprints or Iterations”
Work to be done is captured in a list is called?
A brief statement that describes a piece work that can be executed in a sprint is?
Work broken into 2 to 4 week chunks is called?
How much work a team can get done is called the team’s?
Key Scrum meetings are called?
A project’s scope and progress is visually represented by?
We call the rooms where Agile teams work together?
Anything that prevents the team from making progress?
“Backlog”
“User Story”
“Sprints or Iterations”
“Velocity”
“Ceremonies”
“Artifacts”
“Collaboration Rooms”
“Impediments”
Terms Quiz

24. Questions …
Thank You!
Favorite thinks Video

25. Story: Why Agile