The document discusses how to create great teams and get them started on Agile projects. It defines a team as a small group of people with complementary skills committed to a common purpose and goals. The document recommends that teams learn about each other's skills, determine their purpose and values, review the backlog of stories to work on, and participate in planning activities like estimating story sizes and scheduling work for upcoming sprints. The goal is for the team to work adaptably and commit to delivering working software frequently.

1. Great Team Starts Dan LeFebvre DCL Agility, LLC Dan @DCLAgility.com www.DCLAgility.com 1

2. Teams 2 “A team is a small number of people with complementary skills who are committed to a common purpose, performance goals, and approachfor which they are mutually accountable." (Katzenbach and Smith, 1993)

3. Learn about the process 3 Approach

4. Experienced Agile Teams 4 Core of Agile

5. 5 New to Agile

6. Learn about the team 6 Skills Accountability

7. Market of Skills 7 Skills and abilities relevant to the team I bring Skills and abilities I have under the table Skills and abilities I wish to improve

8. Market of Skills 8 Excitement Skills and abilities relevant to the team I bring Skills and abilities I have under the table Skills and abilities I wish to improve Forgot to mention I can help!

9. Values 9

10. Working Agreements 10 We believe in _________,therefore we will ___________________. Value Done Started Action Done Ready

11. Learn about the work 11 Purpose

12. 12 Newspaper projection

13. Press Release 13

14. Review the backlog 14 Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit>

15. 15 High-Low Showdown

16. Deal and Slide 16

17. Planning Poker on Columns 17

18. Project Velocity 18 Adaptability Commitment

19. Release Planning 19 Sprint 1 Sprint 2 Sprint 3 Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title Story Title As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit> As a <user or role> I want <feature> so that <benefit>

20. Great Starts Summary 20 Core of Agile