© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.

Slides:



Advertisements
Similar presentations
Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.
Advertisements

Feb Alten Group Started in France in 1988 Currently more than people Presence in 10 countries Active in The Netherlands since 2002.
Agile Development Primer – Using Roundtable TSMS in an Agile Shop Michael G. Solomon Solomon Consulting Inc.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
ECE44x SCRUM Overview slides adapted from Marty Stepp
Agile Project Management with Scrum
Process and tools Individuals and interactions over Following a plan Responding to change over Comprehensive documentation Working software over Contract.
Dept. of Computer Science & Engineering, The Chinese University of Hong Kong Agile Software Development CHEN Xinyu
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
An Introduction to Scrum
Agile Methods and Extreme Programming CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 23, 2007.
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Programming with eyes wide open. Your host today Subby Angelov Team
Introduction to Agile.
Agile Methodologies for Project Management By – Komal Mehta.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
AgileCamp Presents: Agile Software Development. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Software Development Landscape
1 Agile Methodology & Programming Ric Holt July 2009.
Chapter 4 Agile Development
Agile Software Development Brian Link
What is Scrum Process? Where is it used? How is it better?
1 SCRUM 22/02/2009 By Siemen Bastiaens >>
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Stephen Chief Strategy Officer Telerik
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
CS3100 Software Project Management Agile Approaches.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Presentation from: See Also: scrumreferencecard.com/ScrumReferenceCard.pdf.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
SCRUM.
PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
 Overview of agile project management  Key concepts and terminology  Available resources and tools  Applicability of agile project management to different.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Introduction to Agile. Introduction Who is this guy?
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Scuola Politecnica Dipartimento DITEN Università degli Studi di Genova An Introduction to Scrum and XP Prof. Riccardo Berta.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Agile/XP Introduction
Manifesto for Agile Software Development
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Agile Software Development Brian Moseley.
Scrum MODULE 3 – Part 3.
روش‌های سريع الانتقال (چابک) توسعه نرم افزار
Adjective: Able to move quickly and easily. Principles and Values
Presentation transcript:

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Agenda  About us  Agile manifesto  Assessing your agility  Assessment methods  Our results  Post assessment

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 3 About us  ANA, Network management platform, developed in NMTG, Cisco  Practicing Scrum, XP for 2 years

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 4 Timeline Pilot team 3 engineers First team ~10 engineers Scale Phase ~30 engineers 10/063/0712/07today 100+ engineers

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 5 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.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 6 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

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 7 Assessment methods  Iteration overview, reflection/retrospective  On going metrics, standard, ad-hoc and custom

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 8 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?

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 Assessing our Agile – Release 1

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 Zoom into Programming

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 11 © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 11 Assessment over releases 1, 2, 3

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 12 Post assessment  Relating to the results  Communication  Act!

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 13 Don't fear change, embrace it. Anthony J. D'Angelo

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 14 Q and A

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 15

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 16 Backup

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 17 “Insanity: doing the same thing over and over again and expecting different results.” Albert Einstein

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 18 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

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 19 Extreme Programming Practices

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 20 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

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 21 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 Held between each iteration. Stories are presented to the customer, as demos. Planning is done for the next iteration. Reflections 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.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 22 Practices taken from Scrum On-site customer 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 ScrumMaster is like a coach, responsible for cheering on the team, being their leader and being their guide Burndown Chart

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 23 Other Practices Roles - Methodologist - Tester - Designer - Documenter - Tracker Measurements

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 24 Team G – Sub release 1-3 © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 24

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 25 Team G – Sub release 1-3 © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 25

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 26 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) © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 26

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 27 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) © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 27

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 28 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? © 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 28