Lightweight Tools for Agile Methods

Transcription

1 Lightweight Tools for Agile Methods Frank Maurer University of Calgary Computer Science e-business Engineering Group (ebe) This presentation reports on joined work with Harpreet Bajwa, Lawrence Liu, Chris Mann, Grigori Melnik, Wenliang Xiong & Carmen Zannier Principles of agile methods ebe Research Overview Overview 3-Feb-06 ebe Research 2 Desktop Technology Program 1

2 Why Agile Methods? CHAOS Report, Standish Group 66% of projects failed or are challenged in 2002 Large projects are failing more often than small projects Only 52% of features make it into product % 28% 26% 27% 16% 31% 15% 23% 28% 40% 51% 49% 46% 53% 33% Succeded Failed Challenged Feb-06 ebe Research 3 Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to 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 That is, while there is value in the items on the right, we value the items on the left more. Kent Beck - Mike Beedle - Arie van Bennekum - Alistair Cockburn - Ward Cunningham - Martin Fowler - James Grenning - Jim Highsmith - Andrew Hunt - Ron Jeffries - Jon Kern - Brian Marick 3-Feb-06 - Robert C. Martin - Steve Mellor ebe -Research Ken Schwaber - Jeff Sutherland - Dave Thomas 4 Desktop Technology Program 2

3 How Everything Fits Together Ken Beck. Extreme Programming Explained: Embrace Change, Addison-Wesley, 1999, p Feb-06 ebe Research 6 Scrum Flow (Sutherland, Schwaber and Beedle) Ken Schwaber, Agile Project Management with Scrum, Microsoft Press: Scrum: 15 min daily meetings Team members respond to basics: -What did you do since last Scrum? -Do you have any obstacles? -What will you do before next meeting? Sprint: 30 days Features assigned to Sprint Desktop Technology Program Potentially Shippable Functionality 3

4 Agile Practices Knowledge sharing ( verbal documentation, co-location) Adaptive Project Management using Informal Feature Description (story cards) Fast feedback (on-site customer, continuous integration, short iterations, retrospectives) Emphasis on testing Emerging (simple) design & refactoring Pairing Collaborative, "whole team approach" Business contracts 3-Feb-06 ebe Research 8 Principles of agile methods ebe Research Overview Empirical studies on agile methods Tools for agile teams Overview 3-Feb-06 ebe Research 9 Desktop Technology Program 4

5 Empirical Research on Agile Methods Are the claims of agilists justified? Issues: Significance versus insight Qualitative versus quantitative Industry-based Perceptions vs reality 3-Feb-06 ebe Research 11 Online questionnaire voluntarily and anonymously Total numbers of respondents: 240 out of 693 invited, 35% response ratio Over 3 years 6 academic semesters 7 courses A Cross-Program Investigation of Students' Perceptions of Agile Methods (Melnik/Maurer) Academic program DIPL (2 years) POSTDIPL (2+2 years) JUNIOR (2 years) SENIOR (4 years) GRAD (4 +2 years) Semester(s) Fall 2001, Winter 2002 Fall 2003 Winter 2002 Fall 2002 Fall 2003 Winter 2004 Winter 2003 Winter 2004 Fall 2002 Winter 2003 Fall 2003 Winter 2004 Winter 2002 Fall 2002 Fall 2003 # of nvita-tions sent out # of respondents Response rate 61% 23% 55% 56% 96% 65% 14% 13% 35% 31% 61% 67% 75% 73% 94% Total, All Programs % 3-Feb-06 ebe Research 12 Desktop Technology Program 5

6 Using XP Improves Productivity of Small Teams I believe that XP helps get more work done in less time and is very effective for small groups as it allows for the group members not to get stuck for extended periods of time % Disagree Disagree Agree Agree Strongly Somewhat Neutral Somewhat Strongly SAIT UofC Junior Undergrads UofC Senior Undergrads UofC Grads 3-Feb-06 ebe Research 13 Comparative Analysis of Job Satisfaction (Melnik/Maurer) Web-based survey (459 complete, 286 partial responses) Some questions verbatim identical with Computerworld survey (936 responses) Overall job satisfaction by groups Agile 0.9% 8.5% 53.2% 29.4% Non-agile (main study) 7.6% 29.8% 21.4% 31.3% 9.9% IT General (supplementary study) 11.0% 25.0% 11.0% 35. 0% 18.0% 3-Feb-06 ebe Research 18 Desktop Technology Program 6

7 Longitudinal Agile Study (Mann/Maurer) Issues: Not much detailed data on agile methods from industry Approach inspired by ethnographical methods and action research Embed researcher for two years in work environment Change environment: Pair programming Continuous integration & test-driven development Scrum project management Observe and collect data 3-Feb-06 ebe Research 20 Scrum Results Overall results: Reduced overtime Increased customer satisfaction % Hours Overtime Average Percent Overtime Worked By Team Windows App 1 support and Windows App 2 Scrum Introduced Development New Windows App Release Website Release Week 3-Feb-06 ebe Research 25 Desktop Technology Program 7

8 Tools 3-Feb-06 ebe Research 28 In-container Portlet Testing (Bajwa/Xiong/Maurer) Portlets Source: (IBM Portal [2]) Portlets 3-Feb-06 ebe Research 29 Desktop Technology Program 8

9 Container-based Software: Testing Issue The Portlet API layer is the only way Portlets and container communicate 3-Feb-06 ebe Research 30 WIT- Design Overview 3-Feb-06 ebe Research 31 Desktop Technology Program 9

10 Requirements and Agile Planning User stories On index cards Short descriptions of a feature In customer language, no techno babble Provide value to customer Independent of each other Testable Small decompose large stories Estimated by developers Collect story cards and prioritize them 3-Feb-06 ebe Research 34 Digital Tables for Agile Planning (Liu/Maurer) 3-Feb-06 ebe Research 37 Desktop Technology Program 10

11 All photos from Current work By drp By curiouskiwi By fallsroad 3-Feb-06 ebe Research 38 Alan: A robotic colleague for agile teams Support continuous integration Create and distribute summaries of Scrum meetings 3-Feb-06 ebe Research 39 Desktop Technology Program 11

12 FitClipse Acceptance test driven development tool Testing of distributed J2EE applications Scenario-driven testing of business logic layer as well as UI layer Acceptance regression testing 3-Feb-06 ebe Research 42 Discussion Desktop Technology Program 12