1. Project Transparency I think a chicken just ate my pig. It wasn’t an accident, it was Agile.
2. Objective As an attendee I can walk away with an understanding of what Agile is and how to dispel common client misconceptions so that I can approach Agile discussions with clients in a non-frightening manner. It wasn’t an accident, it was Agile.
3. Agile Manifesto Individuals and interactionsover processes and tools Working softwareover comprehensive documentation Customer collaborationover contract negotiation Responding to changeover following a plan That is, while there is value in the items on the right, we value the items on the left more.[1] [1]http://agilemanifesto.org/ It wasn’t an accident, it was Agile.
9. How does a benefit? _client complete budget control no black box project scope can change frequent deployable software It wasn’t an accident, it was Agile.
10. How does a benefit? _developer structure constant feedback protection from client requests insight into client requests empowerment more development less documentation fewer requirements It wasn’t an accident, it was Agile.
11. What is Scrum? Scrum is a framework for managing agile projects. It wasn’t an accident, it was Agile.
12. How does Scrum work? Daily meetings (Daily Scrum) Timeboxing Self organizing team (all members have equal voice) Single EMPOWERED voice from client (product owner) Scrum Master prioritizes needs with client Team sets their own timelines It wasn’t an accident, it was Agile.
13. How does Scrum work? Sprint Planning Daily Scrum Sprint Retrospective It wasn’t an accident, it was Agile.
14. Selling Agile explain iterative development model list benefits to client in clear terms transparent process budget control … lay out sample sprints (iterations) speak to past performance It wasn’t an accident, it was Agile.
15. Selling Agile to Government don’t get hung up on terminology transparency is not the key factor for Gov focus on budget control focus on frequent delivery of TESTED software It wasn’t an accident, it was Agile.