The document discusses establishing an agile rhythm through effective agile processes and meetings. It describes key roles in successful agile teams including the Scrum Master, customer, developer, and tester. Organizations implementing agile should accept change, enable customer communication, allow for incremental work, and utilize automated testing and collaborative environments. Core agile processes include initiation, planning, execution, closing, and monitoring. Meetings like product planning, sprint planning, stand-ups, and retrospectives help define goals and maintain rhythm. Tools such as kanban boards and burn down charts also aid in identifying impediments and improving team velocity and rhythm over time.

1. Café Agile
Appetizers
Preparing to Lead
Getting Started
1) The Team
Successful Agile teams are made up of these
roles:
SCRUM Master, Customer, Developer, Tester
and Coordinator
2) The Organization
Organizations that implement successful Agile
processes are committed to:
Change acceptance
Customer Communications
Incremental Work
Automated Testing
Collaborative Environments
Martin L. Harbolt, PMP, CSM, ITIL
3) The Process
Successful Agile processes include:
Initiation
Planning Agile Leadership = Servant Leadership
Executing
Closing
Monitoring and Controlling

2. Entrées
Rhythmic Leadership
Meetings
4) Product Planning
Product Planning defines the end goal and helps the
team define the process and Rhythm to get there.
5) Sprint Planning
Sprint Planning defines the goal for the sprint and
helps the team define the tasks necessary to stay in
Rhythm.
6) Stand Up
Stand up meetings maintain Rhythm and identify
impediments.
7) Sprint Review and Retrospectives
This is your health check. Did we plan well? How
can we plan better?
8) Building a Rhythm
À la Carte
Help the team understand the Rhythm necessary
to be successful. Leadership Principles
Missing Roles Disrupt Rhythm
Dessert Serve the team by validating that all roles are
accounted for and know it.
Follow the Process, Serve the Customer
Leadership with Goodies
Serve the customer by following the process, plan the
Tools product and allow the team to build a Rhythm and the
product.
9) Kanban Board
Negotiate to Maintain Rhythm
Use of a Kanban board can be extremely beneficial. Make
it visible and use it during stand up meetings. Serve the team by negotiating with the customer
when planning the product and sprint schedules to
10) Sprint Burn Down meet the team’s Rhythm.
Sprint burn down helps identify and improve the team Identify Impediments
velocity and subsequently leads to identifying their
Rhythm. Serve the team by identifying impediments. Even if
they are not reported to you, they always disrupt
11) Product Burn Down the team’s Rhythm.
Product burn down helps to identify scope volatility, Build a Rhythm, Don’t Fall Behind
velocity across sprint and overall team Rhythm.
Serve the team by providing a Rhythm, publishing
that Rhythm, sticking to it, and holding the team to it.
12) Life Cycle
Monitor, Small Adjustments
The Life Cycle is a process. Helping the team learn
the Life Cycle and when they can expect certain Serve the team by monitoring the tools (Sprint and
events, improves Rhythm. Product Burn downs) and making small adjustment.
Large adjustments may disrupt the Rhythm.
Twitter: @ProfMartyScrum
LinkedIn: http://www.linkedin.com/in/martinlharboltpmp
Blog: http://askthescrummaster.blogspot.com/