The Agile Buffet Tweet and win: #dpr306

1. DPR306 The Agile BuffetTweet and win: #dpr306 Stephen Forte CSO Telerik @worksonmypc Joel Semeniuk Executive VP Telerik @joel_semeniuk

2. About Joel and Steve Joel Semeniuk @joel_semeniuk Steve Forte @worksonmypc Microsoft Regional Director Certified Scrum Master Microsoft MVP, SQL Azure Telerik CSO • Microsoft Regional Director • Certified Scrum Master • Microsoft MVP, ALM • Telerik Executive VP

3. Is It Ok…? • Is It Ok To Change Scrum? • Can you combine practices and still be Agile? • Can you be Agile if you don’t to TDD?

4. Agenda • Back to the basics: Agile Manifesto • Influential Agile Methodologies • Agile Scenarios –Eating from the Buffet Table

5. Individuals and interactions Responding to change Working software Customer collaboration Following a plan Comprehensive documentation Contract negotiation Process and tools over over over over The Agile Manifesto–a statement of values Source: www.agilemanifesto.org

6. Back to the Basics • “Agile” is about “values” not “rules” and rigid adherence to a process • Agile is about embracing change

7. 12 Principles of Agile • Early and continuous delivery of software • Welcome changing requirements • Deliver working software frequently • Business people and developers must work together daily • Build projects around motivated individuals • Most effective method of communication is face-to-face • Working software is the primary measure of progress • Agile processes promote sustainable development • Continuous attention to technical excellence • Simplicity — is essential • Self-organizing teams • Reflect on how to become more effective

8. Agenda • Back to the basics: Agile Manifesto • Influential Agile Methodologies • Agile Scenarios –Eating from the Buffet Table

9. Influential Agile Methodologies • XP (The Past) • Scrum (The Present) • Kanban (The Future)

10. Extreme Programming (aka XP) • Team of 5-10 programmers • Single location • On Site Customer • Iterative delivery of releasable software • “Requirements” are specified as user stories • Pair Programming • Strict Code Standards • Unit Testing • Emergent Requirements, architecture, and design

11. Core Practices of XP • Sit together • Whole team • Informative workspace • Energized work • Pair Programming • Stories • Weekly cycles • Quarterly Cycles • Slack • Ten-Minute Build • Continuous Integration • Test-First Programming • Incremental Design

12. Prince 2 • Great for governance • Works well w/ Agile Models • http://www.prince2.com/

13. Scrum • An Agile methodology that stresses communication • Time boxed (sprints) development cycles • By design is a revolutionary process • Rigid by nature • Most popular methodology today

14. Scrum

15. Core Practices of Scrum • Cross functional and collocated teams of 8 or less • Develop in sprints of fixed duration • Each sprint delivers incremental, tested functionality to the user • Work within the sprint is fixed • The scrum master mentors and manages the self-organizing and self-managing teams • All work to be done is carried from the Product Backlog • The product owner manages the product backlog • A daily 15 min stand-up meeting (Daily scrum) is primary communication method • Requirements, architecture, and design emerge over time • Empirical Process Control

16. Kanban • Japanese for “signal card” • From the Toyoda production system (Lean) • Define a work flow and visualize it • Organize a queue • Limit work in progress (WIP) for each queue • Allows you to constantly evaluate process improvements • Allow work to flow through the system in a controlled way (not iterative) • No sprints! • Evolutionary by design • Change is built into the model • Communication is about progress (not merely results) • Eliminate Daily Scrum

17. Kanban

18. Core Practices of Kanban • Define and visualize the workflow • Limit Work-in-progress • Measure and Manage Flow • Make Process Policies Explicit • Use Models to Suggest Improvement • For more info: http://finance.groups.yahoo.com/group/kanbandev/message/9261

19. Agenda • Back to the basics: Agile Manifesto • Influential Agile Methodologies • Agile Scenarios –Eating from the Buffet Table

20. Agile is Growing

21. Mixed Methods are the Norm Source: Forrester/Dr. Dobb’s Global Developer Technographics Survey, Q3 2009

22. Agile is like a buffet table • It is ok to mix and match from different agile methodologies • Just make sure your features are compatible • Just make sure you eat healthy ;) http://www.agileproductdesign.com/blog/2009/kanban_over_simplified.html

23. Eating from the buffet table Designing an agile methodology

24. Scenario 1 – New Distributed Project • Characteristics • Remote team in different time zone • Greenfield project • Contractors

25. Core Practices for Scenario 1 • From XP • User Stories • Pair Programming • Continuous Integration • From Scrum • Use Sprints of fixed duration • Daily (virtual) Scrum meeting • From Kanban • Make Process Policies Explicit • Use Models to Suggest Improvement • Limit work in progress

26. Scenario 2 - Maintenance • Characteristics • Reactive • Continual evaluation • Continual delivery • Mix of New Requirements and Bugs

27. Core Practices for Scenario 2 • From XP • Extensive use of Unit Testing • Refactoring and Emergent Design • Continuous Integration • Sit together • Whole team • Informative workspace • Energized work • From Scrum • Daily Standup • Sprints for Improvement Cadences and Reviews • From Kanban • Limit work in progress • Continuous Delivery • Explicit Gates

28. Scenario 3 – Managed Outsource • Characteristics • Customer / Supplier • Cost and Budget Centric • Supplier takes responsibility

29. Core Practices for Scenario 3 • From XP • Extensive use of Unit Testing • Refactoring and Emergent Design • Continuous Integration • Incremental Design • Sit together • Whole team • Informative workspace • From Scrum • Daily Standup • Sprint Planning • Sprints and Sprint Reviews • Customer is Product Owner • Product Owner Reprioritizes against value • From Kanban • Explicit Gates

30. What about the others? • Can you use TDD and use Scrum? • Can you use BDD and use Kanban?

31. Certain Practices Apply Often • Unit Testing • Automated Builds • Incremental and Continual Releases • Emergent Requirements, architecture, and design • Daily rhythm and standups • Engaged Product Owners • Backlogs Managed by Product Owners

32. Start with ScrumPull in Practices via Retrospectives

33. Questions?

34. Recommended Resources • Tom DeMarco • Peopleware • Slack • Fred Brooks • The Mythical Man Month • Parkinson's Law

35. DPR Track Resources • http://www.microsoft.com/visualstudio • http://www.microsoft.com/visualstudio/en-us/lightswitch • http://www.microsoft.com/expression/ • http://blogs.msdn.com/b/somasegar/ • http://blogs.msdn.com/b/bharry/ • http://www.microsoft.com/sqlserver/en/us/default.aspx • http://www.facebook.com/visualstudio

36. Resources • Connect. Share. Discuss. http://northamerica.msteched.com Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

37. Complete an evaluation on CommNet and enter to win!