Agile Assessment Gadi Lifshitz Ayelet Kroskin Barak Yagour
Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1
Agenda § About us § Agile manifesto § Assessing your agility § Assessment methods § Our results § Post assessment Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 2
About us § ANA, Network management platform, developed in NMTG, Cisco § Practicing Scrum, XP for 2 years Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 3
Timeline 10/06 3/07 Pilot team First team Scale Phase 3 engineers ~10 engineers ~30 engineers Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 12/07 today 100+ engineers 4
The Agile Manifesto 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. http: //agilemanifesto. org/ Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 5
Assessing your agility § Why do it? The team Peer teams Upper management § When is it the right time to assess? Post project assessment Predetermined points in time § What aspects are measureable? Basically everything, we chose to focus on foundations of XP Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 6
Assessment methods § Iteration overview, reflection/retrospective § On going metrics, standard, ad-hoc and custom Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 7
Radar chart § Overview § Preparations (Goal setting) § Execution (Data collection) § Analysis § Results (and decision making) Example questions : • Is code checked-in daily by each pair? • Have you paired with everyone in the team? Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 8
Assessing our Agile – Release 1 Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 9
Zoom into Programming Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 10
Assessment over releases 1, 2, 3 Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 11
Post assessment § Relating to the results § Communication § Act! Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 12
Don't fear change, embrace it. Anthony J. D'Angelo Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 13
Q and A Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 14
Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 15
Backup Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 16
“Insanity: doing the same thing over and over again and expecting different results. ” Albert Einstein Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 17
Agile Software Development Methods : • Adaptive • Crystal • DSDM • Extreme Programming (XP) – Focuses on the team • Scrum – Focuses on project management • FDD • Lean Development We take on practices from Scrum and XP Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 18
Extreme Programming Practices Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 19
Practices taken from Extreme Programming (XP) • Planning game The customer prioritizes the user stories. The programmers breakup the stories into tasks. The programmers estimate the tasks. • Customer tests The Customer defines what is it that he wants and how does he want to know it is working Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 20
Practices taken from Scrum • Daily Standup meetings Last about 15 minutes. Each team member updates about what was achieved yesterday, and what he will do today. Standing up during the meeting in order to avoid too much talking … • Business Days • Reflections Held between each iteration. Stories are presented to the customer, as demos. Planning is done for the next iteration. Reflections are held during Business Day and last 1 hour. During reflections, the team discusses what’s going well and what needs improvement. The team members learn from their experiences and adjust their behavior accordingly. • Product Backlog The Product Backlog is the master prioritized list of all functionality desired in the product. The Product Backlog is allowed to grow and change as more is learned about the product and its customers. Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 21
Practices taken from Scrum • On-site customers are responsible for choosing and prioritizing features. The features are then presented to the customer and accepted on business Day. • Scrum master Responsible for improving the lives and productivity of the development team , enabling close cooperation across all roles, removing barriers, shielding the team from external interferences and ensuring that the process is followed. The Scrum. Master is like a coach, responsible for cheering on the team, being their leader and being their guide • Burndown Chart Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 22
Other Practices • Roles - Methodologist Tester Designer Documenter Tracker • Measurements Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 23
Team G – Sub release 1 -3 Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 24
Team G – Sub release 1 -3 Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 25
Questions with maximum score : Does the team demonstrate its progress to the customer at least once per month? (4. 8) Do all team members sit in one room? (4. 8) Is the status of each story checked during the daily standup meeting? (4. 3) Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 26
Questions with minimum score : Do you write tests before writing new code? (1. 12) Have you paired with everyone in the team? (2. 2) Are all acceptance tests and unit tests run daily? (2. 4) Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 27
Questions with largest variance : Have you paired with everyone in the team? Does the integration build currently complete in less than 15 minutes? Is code checked-in daily by each pair? Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 28
- Slides: 28