Becoming "AGILE"

1. Becoming "AGILE" With Teaching Systems Analysis and Design 2012 ISECON Conference - New Orleans, LA

2. Presenters Wayne E PauliDakota State UniversityTom WesselDavisbase ConsultingMitchel BergmanDakota State UniversityZachary AndersonDakota State University 2012 ISECON Conference - New Orleans, LA

3. Workshop Objective • For years the perceived correct way to teach systems analysis and design has been through the traditional approaches and methodologies that have been derived from the Waterfall approach. • Waterfall methodology has been proven to be flawed in its approach to the inherently complex and highly variable software development environment that we are collaboratively targeting • Each of us could research and find data that supports the concept that Waterfall will reduce the likelihood of success in software development The objective of the workshop is to discuss the development of a curriculum that focuses on teaching programming-centric methodologies where modeling and documentation overhead are optimized and face-to-face is the preferred communication route. 2012 ISECON Conference - New Orleans, LA

4. From their Mouth & Actions • Students are telling me the same thing… • During the Systems Analysis & Design class (SAD) I allow them to choose a traditional methodology from which they will work on deliverables of a semester long mythical project. • They choose, RAD, and its versions 3 to 1 over the more traditional methodologies – searching for more flexibility in their development environment •  And, when the 5th Edition of Dennis, etal was released and adopted, I had 29% (14 of 47) choose Agile even though there was not a great deal of content in the text •  They grow terribly frustrated with the building of  Gantt Charts, DFDs, and ERDs 2012 ISECON Conference - New Orleans, LA

5. The Premise • According to (Dennis, Wixom, and Roth) “Agile development practices were created in part because of dissatisfaction with the sequential, inflexible structure of waterfall-based approaches.” • Studies are showing that Agile is making large gains in the development world, and are nearing an even split with waterfall. • Based on this assumption, we have created a framework for a 3 credit undergraduate class and are sharing it today with you through this workshop. 2012 ISECON Conference - New Orleans, LA

6. It All Started… • At a Career Fair • Approached by a major employer to consider bringing Agile into our technology curriculum • OK, tell me why • OK, tell me more • OK, email me your ideas • OK that will get rid of them 2012 ISECON Conference - New Orleans, LA

7. But It Didn’t • What started with Tom Wessel of • Became Tom Wessel of The email did find my inbox, I began reading the books on Tom’s suggested reading list and I came to a conclusion, we need to put Agile into our curriculum at Dakota State University 2012 ISECON Conference - New Orleans, LA

8. What is Agile? • Put simply, agile development is a different way of managing IT development teams and projects. • A small group of people got together in 2001 to discuss their beliefs that the traditional approach to managing software development projects was failing far too often, and there had to be a better way. 2012 ISECON Conference - New Orleans, LA

9. The Manifesto • 4 important values that are as relevant today as they were in 2001. It says: “we value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan 2012 ISECON Conference - New Orleans, LA

10. 10 Key Principles of Agileaccording to Kelly Waters - 2007 1. Active user involvement is imperative2. The team must be empowered to make decisions3. Requirements evolve but the timescale is fixed4. Capture requirements at a high level and elaborate in a JIT manner; lightweight & visual5. Develop small, incremental releases and iterate 6. Focus on frequent delivery of products7. Complete each feature before moving on to the next8. Apply the 80/20 rule9. Testing is integrated throughout the project lifecycle – test early and often10. A collaborative & cooperative approach between all stakeholders is essential 2012 ISECON Conference - New Orleans, LA

11. Agile Development What it isn’t Stresses teamwork Stresses iteration Stresses customer Stresses embracing change A fix all, do all A left wing theory Void of documentation A replacement for traditional SAD What it is 2012 ISECON Conference - New Orleans, LA

12. October 2012 Discussed Agile and reported some interesting statistics… 2012 ISECON Conference - New Orleans, LA

13. PMI Agility Report • The “Pulse of the Profession Organizational Agility report” found that of projects at organizations utilizing agile development that: • 73% finished on time • 75% finished on budget • 83% meet goals and business objectives • 71% meet or exceeded ROI 2012 ISECON Conference - New Orleans, LA

14. The Private Sector View Tom Wessel Program Manager and Agile Coach Davisbase Consulting Charlotte, NC Why should higher Ed embrace Agile? 2012 ISECON Conference - New Orleans, LA

15. Who I Am • Tom Wessel – Davisbase Consulting • Passion for optimizing the SDLC process and growing high performing software development teams • 20 years in software development in the areas of: Quality Assurance & Control, Technical Support, Development, Project & Program Management, training & coaching • 6 years working in Agile in the areas of: training, coaching, and consulting. • Trained over 1,000 people and coached over 100 teams ranging from start-ups to Fortune 50 corporations. 2012 ISECON Conference - New Orleans, LA

16. Why I Am an Agile Coach • Agile is a perfect fit for my passion: • it makes sense for software development, emphasizing empirical process to address the complexity and high variability associated with software creation • it is about people – the key to great software are great teams • it is about flow – minimize WIP to improve cycle and lead times 2012 ISECON Conference - New Orleans, LA

17. Public/Private Collaboration • High Demand for Computer Science graduates since technology touches all facets of business • The Public/Private relationship is a symbiotic one • Public institutions should seek input and guidance from the private sector as to what skills are needed. • Public Institutions should provide students with the skills required • Private institutions should create a pipeline for students in the form of internship and employment opportunities 2012 ISECON Conference - New Orleans, LA

18. The Evolution of Agile • Agile is becoming mainstream because of its ability to generate greater business value sooner with better quality and risk management. • Knowledge of and experience in agile principles and practices, especially development practices, is increasing in demand. • The need to scale Agile across organizations is growing. • It is a mind set, not just a set of principles and practices, that requires the continuous pursuit of excellence. 2012 ISECON Conference - New Orleans, LA

19. So, What About The Curriculum • Based on a 16 week semester • 3 credit hours • Designed to be an upper level major specific class • The traditional SAD course would be a prerequisite • All work completed in teams • All examinations completed individually 2012 ISECON Conference - New Orleans, LA

20. Topics • Introduction to Agile • Compared with traditionalapproaches • Scrum • Extreme Programming • Lean • Five levels of Planning • Agile Artifacts • Agile Roles • Agile Requirements • Agile Estimation • Agile Testing • Agile Development (expanded next slide) 2012 ISECON Conference - New Orleans, LA

21. Agile Development • Five weeks of more intensive team work focused on areas such as: • Software Configuration Management • Unit Testing • Design Patterns • Continuous Integration • Coding Standards • Test Driven Development • Pair Programming • Refactoring 2012 ISECON Conference - New Orleans, LA

22. Sprinkle In Some Private Sector • The course will also utilize five private sector presentations to bring the real world into the theory to be taught in the class room. • Wells Fargo has created a case study for the students to utilize as their material for the deliverables. 2012 ISECON Conference - New Orleans, LA

23. CIS 492 • 64356 CIS 492 D01  Topics: Agile Development    3cr   on-campus   Wayne Pauli • Sandy Anderson • Registrar 2012 ISECON Conference - New Orleans, LA

24. So, What About The Students • I had the private sector on board • I had my Dean on board • So I made my pitch to two students • Different backgrounds • Different fields of study • Both had been top students in the traditional Systems Analysis and Design course • Both had completed internships with large but different financial institutions 2012 ISECON Conference - New Orleans, LA

25. Scrum This Thing Called Scrum Mitch Bergman Information Systems major 2012 ISECON Conference - New Orleans, LA

26. What is Scrum? • Iterative and incremental development method • Each output’s iteration is an increment of the product • Framework rather than full process • Much is left up to the development team • Team work 2012 ISECON Conference - New Orleans, LA

27. Why Use Scrum? • Along the way, Scrum allows for: • Easy adaptations • Quick changes • Bug fixes • Quickly changing technology 2012 ISECON Conference - New Orleans, LA

28. Scrum Structure • Sprints • Timeboxed iteration • No more than one month • Driven by requirements list (product backlog) • Sprint Planning • Team looks at requirements • Analyze available technology • Evaluate skills/capabilities 2012 ISECON Conference - New Orleans, LA

29. Scrum Meeting • Keep it short! 15 minutes • Who attends? • ScrumMaster, product owner, team • Team shares: • What they have done in the past 24 hours • What they are going to do in the next 24 hours • What might get in the way 2012 ISECON Conference - New Orleans, LA

30. Scrum Roles • ScrumMaster • Provides leadership, guidance, and coaching • Expert of the Scrum process • Product Owner • Represents the business, customers, or users • Vision for the product • Prioritizes items on the product backlog • Team 2012 ISECON Conference - New Orleans, LA

31. Benefits of Scrum • Respond more accurately • Breaks down complex development • React to changes and problems more quickly 2012 ISECON Conference - New Orleans, LA

32. This Thing Called Extreme Programming Zach Anderson Computer Science Major 2012 ISECON Conference - New Orleans, LA

33. Four Variables • Cost • Time • Quality • Scope 2012 ISECON Conference - New Orleans, LA

34. Four Values • Communication • Simplicity • Feedback • Courage 2012 ISECON Conference - New Orleans, LA

35. Planning • User Stories • Estimation • Acceptance Tests 2012 ISECON Conference - New Orleans, LA

36. XP Principals • Coding Standards • Test Driven Development • Collective Code Ownership • Paired Programming • Refactoring 2012 ISECON Conference - New Orleans, LA

37. Coding Standards • Code is more readable and uniform • Developing Standards • Agree on basic standards and grow them from there 2012 ISECON Conference - New Orleans, LA

38. Test Driven Development • Write the test before implementing the change • Each test should cover no more than 5 to 10 minutes of programming 2012 ISECON Conference - New Orleans, LA

39. Collective Code Ownership • No one person “owns” any code • Don’t count on keeping it • Keep it simple 2012 ISECON Conference - New Orleans, LA

40. Paired Programming • Always have two people developing code • Driver/Navigator • Reduces errors • Enforces Standards • Easier to read • Navigator can begin thinking about the next test to be written 2012 ISECON Conference - New Orleans, LA

41. Refactoring • Old code is wasted time and space • Change the code, not the result 2012 ISECON Conference - New Orleans, LA

42. A New Language A new way of thinking A new way of developing software A new approach to teaching development techniques 2012 ISECON Conference - New Orleans, LA

43. Artifacts Sprint Agile Scrum Velocity Scrum Master Pair Programming Backlog Lean 2012 ISECON Conference - New Orleans, LA

44. Contact Information Wayne E Pauli wayne.pauli@dsu.eduDakota State UniversityTom Wessel tom.wessel@davisbase.comDavisbase ConsultingMitchel Bergman mjbergman15551@pluto.dsu.eduDakota State UniversityZachary Anderson zlanderson@pluto.dsu.eduDakota State University 2012 ISECON Conference - New Orleans, LA

45. QUESTIONS Thank you for attending Thank you for your Interest 2012 ISECON Conference - New Orleans, LA

46. Resources • Works Cited • Adkins, L. (2010). Coaching Agile Teams. Boston, MA: Pearson Education, Inc. • Bjornvig, J. O. (2011). Lean Architecture. Great Britain: John Wiley and Sons, Ltd, Publication. • Cohn, M. (2004). User Stories Applied. Boston, MA: Pearson Education, Inc. • Dennis, A., Wixom, B., & Roth, R. (2012). Systems Analysis & Design. United States: John Wiley & Sons, Inc. • Gale, S. (2012). Agility Ability, Project Managers Institute, retrieved from www.PMI.org • Gregory, L. C. (2011). Agile Testing. Boston, MA: Pearson Education, Inc. • Larsen, E. D. (2006). Agile Retrospectives: Making Good Teams Great. Unites States of America: Esther Derby & Diana Larsen. • Poppendieck, M. a. (2007). Implementing Lean Software Development. Boston, MA: Pearson Education, Inc. • Pugh, K. (2005). Prefactoring. Sebastopol, CA: O'Reilly Media, Inc. • Pugh, K. (2011). Lean-Agile Acceptance Test-Driven Development. Boston, Ma: Pearson Education, Inc. • Whitaker, K. (2010). Principles of Sotware Development Leadership. Boston, MA: Course Technology PTR. 2012 ISECON Conference - New Orleans, LA

47. 2012 ISECON Conference - New Orleans, LA