6. Three steps to a high performance team Get (and keep) the right players Create conditions for them to thrive and team Manage with lean techniques and selective measures
8. “Stars” are simply more productive . . . Numerous studies show a 10-time difference in productivity and quality among software developers and teams. A tale of two developers . . . Jim Drew
19. Send kids to college.Source: Adapted from Daniel H. Pink, Drive: The Surprising Truth About What Motivates Us, Riverhead Hardcover, 2009
20. Three steps to a high performance team Get (and keep) the right players. Create conditions for them to thrive and team. Manage with lean techniques and selective measures
21. Creating a climate that attracts “stars” Three cultural elements that create space for (and attract) intrinsically motivated development team members: Autonomy Mastery Purpose Source: Daniel H. Pink, Drive: The Surprising Truth About What Motivates Us, Riverhead Hardcover, 2009
32. Three steps to a high performance team Get (and keep) the right players. Create conditions for them to thrive and team. Manage with lean techniques and selective measures
34. Wastes that impede flow Manufacturing sources of waste: App dev. equivalents: Overproduction Waiting (time on hand) Unnecessary transport or conveyance Overprocessing or incorrect processing Excess inventory Unnecessary movement Defects Unused employee creativity Too many superfluous artifacts Broken builds Too many tool transitions Rigid architectures Analysis paralysis Late discovery of defects Rising downstream labor costs Polluted supply chain management (SCM) streams High null-release ratios
35. Key ALM processes that improve “flow” Portfolio management Production planning closed loop Project management JIT Demand Management Build and software configuration management Deployment Release management Change management Service management Testing and quality assurance Change aware continuous integration Change aware configuration management Release management closed loop Production control closed loop
37. Forrester case studies on high performance teams Atlassian Ultimate Software Sabre Holdings CI&T Netflix Funambol For more, see: www.forrester.com/masstlc
50. Selected Forrester research November 3,2010, “Best Practice: Building High-Performance Application Development Teams” April 8, 2011, “Case Study: Sabre – A Culture Of Engagement” March 7, 2011, “CI&T – High Performance, Brazilian Style” January 14, 2011, “Atlassian Creates An Innovation Culture That Produces Results” November 3,2010, “Ultiamate Software Reinvents Its Development Shop To Stay On Its Game” November 2, 2010, “Software Development Archetypes – What’s Your Sign?”
51. Selected bibliography Netflix: Reference Guide on our Freedom & Responsibility Culture (http://www.slideshare.net/reed2001/culture-1798664) Daniel H. Pink, Drive: The Surprising Truth About What Motivates Us, Riverhead Books, 2009 Malcolm Gladwell, Outliers: The Story of Success, Little, Brown & Co., 2008 10X Software Development (http://forums.construx.com/blogs/stevemcc/default.aspx)
Notas do Editor
Delete second Name/Title if not needed, but be sure to keep the Month Day, Year information. For a teleconference, after the date, add a period and “Call in at XX:55 p.m. Eastern time” (change the time to five minutes prior to the start of the teleconference).
Source: Construx Conversations (http://forums.construx.com/blogs/stevemcc/archive/2008/03/27/productivity-variations-among-software-developers-and-teams-the-origin-of-quot-10x-quot.aspx)Sackman, Erikson, and Grant (1968). They studied professional programmers with an average of 7 years’ experience and found that the ratio of initial coding time between the best and worst programmers was about 20 to 1; the ratio of debugging times over 25 to 1; of program size 5 to 1; and of program execution speed about 10 to 1. They found no relationship between a programmer’s amount of experience and code quality or productivity.1968 – Sackman, Erickson and Grant1981 – Curtis1983 – Mills1985 – Demarco and Lister1986 – Curtis et al.1987 – Card1988 – Boehm and Papaccio2000 – Boehm et alThis ratio is characteristic of heuristic work