NAME. Workshare Interest in Agile We realised that lack of a defined process leads to: Unpredictability Repeated errors Wasted effort We were disappointed.

Slides:



Advertisements
Similar presentations
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Advertisements

AGILE DEVELOPMENT Outlines : Quick Look of agile development Agility
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Alternate Software Development Methodologies
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
NAUG NAUG Knowledge Evening – th February 2007.
Agile
Review: Agile Software Testing in Large-Scale Project Talha Majeed COMP 587 Spring 2011.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Applied Software Project Management 1 Introduction Dr. Mengxia Zhu Computer Science Department Southern Illinois University Carbondale.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
An Agile View of Process
Effectively applying ISO9001:2000 clauses 5 and 8
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Scrum Fundamentals: Analyst to ‘Agilist’ By Louis Molnar (C) IAG Consulting 2009 The Agile Business Analyst By: Louis Molnar.
Implementing Total Quality Management
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
CompSci 230 Software Design and Construction
Software Development Landscape
1 Department of Computer Science, University of Sheffield An introduction to eXtreme Programming Professor Mike Holcombe.
Agile Software Development Brian Link
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXtreme programming.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
Embracing change with Extreme Programming Method Engineering Erik ten Brinke
Industry SDLCs and Business Climate. Justin Kalicharan Credentials Director and Senior Technology Officer Over 14 years of coding experience in various.
Information Development Projects
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
1/7/2004CSG - Project Delivery at UT Austin1 Making a Model Perform Adopting a methodology to your environment.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
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.
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
IS3320 Developing and Using Management Information Systems Lecture 20: Project Management Rob Gleasure
Software Engineering (CSI 321) An Agile View of Process 1.
A Team Members Guide to a Culture of Safety
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
AGILE XP AND SCRUM © University of LiverpoolCOMP 319slide 1.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
1. ENTERPRISE AGILE TRANSFORMATION AT THE US POSTAL SERVICE MAY 24, Agile Business Solutions.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
Creating Positive Culture through Leadership (Recovery Orientation) Jennifer Black.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Project Management Software development models & methodologies
Skiing and Boxing Coaching Product and Enterprise Teams 黃馨誼 蘇育光 修訂.
Software Development - Methodologies
Appendix B Agile Methodologies
Владимир Гусаров Директор R&D, Dell Visual Studio ALM MVP ALM Ranger
Agile Software Development Brian Moseley.
Software Engineering (CSI 321)
What do you need to know about XP?
Agile Development – a new way of software development?
Appendix B Agile Methodologies
Agile software development
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

NAME

Workshare Interest in Agile We realised that lack of a defined process leads to: Unpredictability Repeated errors Wasted effort We were disappointed by: Slipping schedules Growing budgets Poor quality We realised we needed to change but investigation of traditional methods showed us that these were not what we wanted. We value quality and innovation and we believe that agile methods assist us in practising them.

Workshare Interest in Agile (2) The emphasis in Workshare Engineering is on an open culture and facilitating communication and learning. Our employees are considered to be intelligent enough to manage their own activities on a day-to- day basis. Management focus is on removing barriers to success, coaching and mentoring. The agile manifesto values people over process. This aligns agile development with the Workshare philosophy.

Motivation Workshare corporate values include a heavy emphasis on quality and teamwork but:  Approximately 70% of development effort was spent on bug fixing.  Reliance on QA to determine quality.  Slipping deadlines  No real process.  No control Almost as fast as specifications could be written down, they became outmoded. Communication between Support, Sales, Product Management, Development and QA was often incomplete. Unit tests were the exception rather than the rule. We were relying on QA to spot errors and defects within the code rather than building quality in.

Motivation (2) = Release Spike defects per week prior to XP Chaotic process No predictability

XP at Workshare Workshare has been practising XP/ agile development since February We employed American XP consultants, Object Mentor to help us. Six senior staff were despatched to their training facility near Chicago to attend XP Immersion VI. Object Mentor programming and business coaches came back with us for three months, to assist in the transition. They demonstrated the value of XP to the developers, then coached them in the practices.

XP at Workshare (2) Workshare have adopted all of the XP values, principles and practices. The members of the Workshare engineering team used the XP values, principles and practices to define their own system. We continually try to think of ways to improve and fine- tune the process, refining our knowledge and techniques.

XP at Workshare (3) - The Story Cycle Customer Planning Meeting Release Planning Meeting Product Management Release Story List Project Iteration Planning Meeting Iteration Story List Development Quality Assurance Sales Engineers Biz Dev Customer Service Business Sign off STG

XP’s Success at Workshare Our original goals for the adoption of XP were: 1.Improve the quality of our products. 2.Better focus on customer and market requirements. 3.Increase communication and teamwork within the Engineering Department. 4.Reduce time to market. 5.Make software development predictable. We believe that the adoption of agile techniques at Workshare has been an unmitigated success.

XP’s Success at Workshare defects per developer per week

Success Factors "I helped the Workshare team transition to XP earlier this year and one thing that really threw me was how terrifyingly well everyone worked together. They are simply the best gelled day-to-day work team I've seen in about seven years." Mike Feathers of Object Mentor Workshare have always believed in teamwork and have always encouraged self-management and empowered our employees. The use of external coaches was another major factor in our success. To have an expert on-site is invaluable. The change model was explained to us by our coaches so we understood the process of change before we embarked upon it.

Inhibitors to Agile Techniques We found no inhibitors to agile methods at Workshare. This is because we already had an open and honest culture that is focused on learning and the delivery of quality. Other (closed) cultures may not have the same success that we have had. The coaches just suggested improvements that might be made. The team were intelligent enough to evaluate them critically and, depending on the result of the evaluation, either accepted or rejected them. Changes either become adopted as part of the new system or they don’t.

Success factors at Workshare Support from Top Management Big Bang start but slow transition before a return was expected A certain level of dissent and questioning was tolerated – so long as people had the courage to try something and express what worked and what did not. Consultancy worked with each engineering team through individual sessions and collectively. The aim being to create a level of ‘trust’ between each team. Workshare Teamwork and determination made it work.

Impact of XP on the business Improvement in the communication of Release Dates Improvements to beta release programme – lead to the creation of a Solutions Engineering team. Escalation and Prioritization of potential stories required sensitive and specialist management – so a Product Quality team was created to help manage escalations and expectations Improved Story definition reduces defects – Strategic Technology team was created to define the more complex stories. Defined process – lead to replication of the same process in South Africa. The success of XP in Engineering enabled elements of XP to be reproduced across the business eg Marketing – story based planning and Customer Service – morning stand-ups.

Long term goals The challenge of ISO 9001:2000 certification and GAMP 4 pharmaceutical compliance Embracing the best Agile methodologies further improvements to the process. Moving XP into the mainstream – recognition from regulatory bodies that there are other models than the waterfall, e.g. Gamp 4 requirements Recognition as a promoter of Best Practice in software development Improve quality of everything.

Staying Agile, Being compliant.. Planning Regression Performance UAT Testing Release Requirements Test Planning Development Planning Game Integration Story Testing Feedback Functional Spec User Requirements Walkthrough / Inspection Validation Procedure Test Results Source Code Use Cases Certified Test platforms WORKSHARE ENGINEERING PROCESS Stories Bluesky Pair Programming Pre QA Star Teams QA Scripts Test Platforms Release Reports Release Notes Siebel Release Procedure Usability /Test Results Support Escalation Procedure Change Control

Future evolution of XP Evolution not replacement of agile methods Movement of agile methods into the Mainstream – from set of practices to methodology ?? New Paradigm …

NAME