Northeast Wisconsin Agile Users Group

1. Northeast Wisconsin Agile Users Group Inaugural Meeting Welcome! Enjoy the Food – Meeting Starts at 6 pm September 16, 2009

2. Northeast Wisconsin Agile Users Group Introductions and Kick Off Tom Burzinski Director of IT and Business Consulting Skyline Technologies, Inc. September 16, 2009

3. Our Sponsors Tonight Fox Valley Technical College - Facilities Skyline Technologies, Inc – Food, Web-site, and Staff, etc. Thank You!

4. Agenda • Mission of the NEW Agile Users Group • What Does It Mean to be “Agile”? • Agile Approaches • Building our NEW Agile Users Group

5. NEW Agile Users Group – Background • What’s Been Done So Far (by Skyline) – • Temporary Users Group Mission and Goals • Temporary Users Group Organization Structure and Bylaw • Stood Up a Ver. 1 of a Users Group Website • Communicated Users Group to NEW • Organized First Meeting • What’s Left to Do (by All of Us) – • Finalize and Approve Users Group Mission and Goals • Finalize and Approve Users Group Bylaws • Nominate and Select Users Group Board • ??????

6. NEW Agile Users Group Mission • Provide members with education on Agile Principles, tools, techniques, etc. • Share Agile knowledge amongst practitioners • Forum for the exchange of information • Networking with others in the Agile community • Have fun while advancing Agile in NEW Provide Agile tools, techniques, and information that you can use companies.

7. Agenda • Mission of the NEW Agile Users Group • What Does It Mean to be “Agile”? • Agile Approaches • Building our NEW Agile Users Group

8. Agile Introduction Bob Schommer, CSM, PMP Senior Project Manager Skyline Technologies, Inc.

9. Iterate, Iterate, Iterate, … • Iterative and incremental development (IID) • Working software in each iteration • Evolutionary and adaptive • Inspect and adapt • Visibility • Iterative and adaptive planning • Risk driven • Client driven • Time boxed

10. History • 1957: IID was used on NASA’s Project Mercury • 1970’s: Successful use on numerous large, life-critical systems (e.g. space, avionic, defense) • 1992: Canadian ATC system • 1994: DoD adopts new standard that prefers iterative and evolutionary methods • 1995: Jeff Sutherland and Ken Schwaber first formalized Scrum • 2001: Agile Manifesto emerged during a weekend meeting of seventeen “agilites” in Utah

11. Agile Manifesto “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more.” www.agilemanifesto.org

12. Agile Principles • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

13. Agile Principles • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity – the art of maximizing the amount of work not done – is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

14. Agile Thinking Traditional Methods Agile Approach Scope Scope Prioritized by business value Scope drives budget and schedule Budget and schedule drives scope Cost Time Time Cost It is impossible to fully define requirements until the client actually begins to use the product.

15. Why Agile? • For the Business • Better able to compete in an ever changing market place • Final product better matches client needs • “Delivered what you needed, not what you asked for” • Adaptable to changing requirements • Focus on delivering value all the time • Lower risk • Higher quality • Greater visibility • Predictability • Optimal use of resources and happier teams

16. Why Agile? • For the Team • People are more important than process or technology • Empowers members to take control and make a difference • Confidence and satisfaction • Improved communications • Between client and team • Within the team • Greater motivation and productivity • Avoids “death marches” that are typical at the end of a project delivered via traditional methods

17. Agenda • Mission of the NEW Agile Users Group • What does it mean to be Agile? • Agile Approaches • Building our NEW Agile Users Group

18. Agile Approaches • Scrum • Extreme Programming (XP) • Crystal Methods • Unified Process (UP) • Dynamic Systems Development Method (DSDM) • Feature Driven Development (FDD) • Lean Development • Adaptive Software Development • Evolutionary Project Management (Evo)

19. Which one should I pick? • It depends: • Likely not a single answer • May need to extend or reduce • Discipline vs. flexibility • Ceremonies • Artifacts • Metrics • Culture • Team skills To be agile, your methodology must be agile.

20. What should I consider when implementing agile? • People • IT • Business • Company culture and commitment • Project complexity and type • Team size • Criticality of solution • New development • Change management • Technology enablers • Location of team members • Regulatory requirements • Sarbanes-Oxley • HIPAA

21. Agile Skeleton and Heart • Skeleton – Build the right thing • Fairly easy to implement • Within weeks for many • Customers begin seeing improvement • Productivity improvements • Heart – Build the thing right • Can be more difficult • Can take months or even years • Change in culture, behavior and organization • Opportunities are exciting!

22. Where Can I Find Help – Agile Resources • Web Sites • www.agilealliance.org • www.scrumalliance.org • www.newagile.org • Books • “Agile and Iterative Development: A Manager’s Guide” by Craig Larman • “Agile Estimating and Planning” by Mike Cohn • “Agile Project Management with Scrum” by Ken Schwaber • NEW Agile Users Group

23. Questions

24. Agenda • Mission of the NEW Agile Users Group • What does it mean to be agile? • Agile Approaches • Building our NEW Agile Users Group

25. Timeline for Next Four Months

26. Proposed Structure

28. Getting Started Tonight • Positions (Agile Users Group Board) – Temporary until Jan 2010 Elections • President: Tom Burzinski (Product Owner) • Vice President: Bob Schommer (ScrumMaster) • Treasurer (TBD) • Secretary/Communications Committee (TBD) • Program Committee (TBD) • Membership Committee (TBD) • Each Scrum team (committee) will have: • ScrumMaster to facilitate the planning sessions (through Jan 2010) • Product Owner to collect and prioritize requirements (through Jan 2010) • Each Product Owner will serve on Board (through Jan 2010) • Committee team members to work on committee bylaws (due in Nov 2009) • Volunteers are needed for all Board positions and committees • ScrumMaster to facilitate tonight’s committee planning sessions • Team members to determine how to complete tasks by November meeting

29. Before We Take a 10 Minute Break • Please fill out an evaluation form • Your feedback is important to us • Next meeting • November 12, 2009 5:30 pm (Thursday) • Fox Valley Technical College: Room TBD • Speaker: TBD