Agile Software Development
|
|
- Jacob Ellis
- 8 years ago
- Views:
Transcription
1 Agile Software Development Use case for Agile Software Development Methodology in an Oil and Gas Exploration environment. White Paper
2 Introduction No matter what business you are in, there are critical systems, processes, and work flows controlled by computer software. The users have a wish list about how the software could be improved to help them do their jobs faster, cheaper, or more accurately. Often the wishes are complex or conflicting, and the present setup is not well documented. You would like a methodology, exploratory in nature, that allows you to discover a path towards better software without wasting time on arduous documentation. You would like a methodology as flexible as the team you employ, the very team generating these use cases. You would like a methodology for getting these modifications into production. You would like a methodology as nimble as you are. What you need is Agile. Agile promotes adaptive planning, evolutionary development and delivery, and a timeboxed iterative approach. Agile Primer Agile software development represents a sequence of iterative steps that leverage the collaboration of interdisciplinary self-organizing teams to develop requirements and incrementally arrive at solutions. A common description of Agile is that it promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle. To better understand Agile, let s first take a brief look at the more classic waterfall method. The Waterfall (Classic) Method The Waterfall method has been around since the early days of software design. A borrowed methodology from manufacturing and distribution, it takes a linear approach to development. This classic method involves gathering every possible requirement up front and proceeding stepwise through design and implementation. The basic steps of the Waterfall Method are: 1 Requirements specification Design Coding Integration Testing and debugging Installation Maintenance Lessons learned through development are documented, not integrated into the current iteration, and used to inform subsequent redesigns. This approach focuses on delivering a fixed work scope while limiting scope creep, and there are situations in which it functions quite well. 1 Royce, Winston W. Article published in 1970, Managing the Development of Large Software Systems Waterfall development is well suited to projects where there is limited complexity, the requirements are well known at the outset, and the software is not highly integrated with other business processes. Imagine a development project to design a system for recording grades for an elementary school. Waterfall can be a great method for delivering this type of project on a predictable cost and schedule.
3 Waterfall Characteristics Requirements & Tasks are well defined at outset. Methodology is highly document driven. Project roles are highly structured and well defined. Communication is through PM and Sponsor. Development cycles are typically long. Project moves forward only after current step is perfected. Progression always moves forward, never backward The Cone of Uncertainty Before we explore Agile software development methodology, we must first understand how knowledge unfolds during the course of a project. Project Management frameworks look at this knowledge expansion inversely as a diminishing uncertainty. At the time of project conception, we know little and uncertainty is high. As we move through the period of definition and requirements gathering, we begin to know more. The process of design and coding gives us more information, further diminishing uncertainty. By the time of project completion we have reduced uncertainty almost completely. This process can be represented by a Cone of Uncertainty. You can see that the Waterfall method drives the bulk of project decisions at the time when uncertainty is greatest, which for a project of any complexity is a risky approach. Given the level of project complexity in exploration software, the rapidly changing science and technology in this area, and our inability to know everything before the start of a project, how can we develop software for this industry that hits the mark, contains costs, and benefits from the increasing knowledge gleaned over the project life? Enter Agile.
4 The Agile Manifesto 2 In 2001 seventeen software developers with a history of working in lightweight project management environments met to talk, ski, relax, and try to find common ground. The result of that meeting was the Manifesto for Agile Software Development which describes best practices in their field. 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 process and tools Working product over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan While there is value in the items on the right, we value the items on the left more. Shared Vision Agile software development depends heavily on a cohesive vision shared by the customer and the development team. Working closely together, the team can iterate quickly through project cycles. Roles under a Bluware Agile project look generally like this: Upper management: the financial buyer who decides to invest budget in development Customer: person at client with the problem to be solved Product Owner: the single business voice available daily to make all business decisions. This role replaces the documentation of more traditional methods Scrum Master: consulting project manager, working side by side with Product Owner Scrum Team: self-directed development team which may be a mix of Bluware and client employees with cross-functional skills that divide the work in accordance with their abilities Together, following the shared vision, the team goes through the Agile process. Agile Process The process and terms below describe the Agile method referred to as Scrum, the most common methodology Bluware employs for software development. Any meetings are public and include the Product Owner, Scrum Master and Team to foster transparent communication. User stories capture the ideas and use cases presented by end users in everyday business language. They are generally short and capture the idea of a problem and the benefit from solving it. They generally follow a format of As a [role], I want [solution] so I can [benefit]. These user stories help the customer decide which features reach the product backlog. Product backlog contains the user stories the customer is considering for development into the soft- ware. Features chosen for development in a project move to the Release Plan. 2 The Agile Manifesto; The Release Plan contains the user stories approved for development in the current project, along with acceptance criteria for each story to clarify how the team will test whether the software is working.
5 The Sprint Planning Meeting is the forum for deciding which items and features from the Release Plan are going into the next development cycle, or sprint. The features for the next cycle are put into the Sprint Backlog. Each Sprint is 1-4 weeks long with daily, face-to-face Scrum Meetings to discuss what each person did the previous day, what they plan to do today, any roadblocks, and an estimate of time remaining. These meetings run less than 15 minutes, and provide both direct feedback into the current sprint and indirect feedback to the product backlog, helping determine which features move to the next in the sprint backlog. At the end of each sprint delivery of working software defines success. The team conducts a sprint review to demonstrate the software, to learn from successes and mistakes and to incorporate that learning into the next sprint planning meeting. Each step of the process works together to give the customer control of the whole project - not just the very beginning of it. Daily Scrum Meeting Indirect Feedback 24 hours 2-4 weeks Wish List User Stories Product Backlog Sprint Planning Sprint Backlog Potentially Shippable Product Increment Direct Feedback Process Improvement Sprint Review Customer Experience Developer Experience Agile Values The writers of the Agile Manifesto developed several principles summed up in the following values: Communication. Collaborate and talk face-to-face. Proximity matters. Simplicity. Do the simplest thing that will work. Simple rules lead to complex behavior. Complex rules lead to [simple] behavior. - Dee Hock, founder and former CEO of VISA Respect. Care about each other. Care about the project. Courage. Honesty results in effective action, fear of bad news results in paralysis. Feedback. The sooner we know about something, the sooner we can adapt and improve.
6 For complex projects Agile methodology offers numerous benefits to the software development team and to the customer Agile Illustration Agile is the perfect development methodology for creative projects, mission critical projects, new technology introductions, new process designs, and projects with poorly defined goals. Science moves at such a rapid pace that it is almost impossible to know everything you need to know before the start of a project. Compounding this factor, science and technology often change in the middle of a project. In a waterfall project you must include any innovations at the start or wait until launch of the next project. With Agile, however, you can adapt to innovations comparatively on the fly gaining the advantage of new technology when you need it most. Bluware s work in the following case illustrates Agile on a real project. The project: Spectral decomposition plug-in component The team: Sprint duration: 6 people; both full and part time four weeks (variable to coordinate with release dates of other software). Number of sprints: 12 Project duration: 12 months Project description: The project goal was to develop a software component that performed spectral decomposition on seismic data. The software used single trace for selecting algorithm and parameters, with rapid computation speed, and then performed computation for an entire event to do quality control over the entire surface. Finally, spectral decomposition was done over an entire volume. This stepwise progression meant less time wasted processing volumes with the wrong algorithms. The customer s research group had developed multiple specialized algorithms to allow for different types of spectral decomposition. Bluware converted these research computations from MATLAB to industrial strength C++ for use outside of the research environment. The team developed a full, interactive user interface with substantial graphics to allow users to select appropriate algorithm and associated parameters, and to visualize quality control results. Special challenges: This was the customer s first Agile project, especially for Product Owner. Moving to a new development methodology created some fear of project failure for the client. This fear was overcome by a significant education process, longer sprints tending toward 4 weeks rather than 1, and ulti- mately successful delivery. The Product Owner doubted that Agile would work and was concerned about a loss of control. Is- sues were resolved through a highly responsive development team and the delivery of functional software at the end of each sprint to allow the Product Owner to offer feedback on the adjustment of algorithms and the user interface. In a traditional waterfall method, this input would not have been possible until project end. Scalability from 1 to 2 to 3 dimensional computed regions result in associated performance degradation. The multiple, short sprints inherent to Agile resolved the dimensional scale issue. The Product Owner was able to discover the issues during development and optimize algorithms and multi-threading application in later sprints after key functionality was delivered.
7 The software component needed to plug-in to multiple versions of product. Bluware resolved this issue by working closely with other product development teams, and maintaining a flexible architecture. Requirements like the choice of algorithms, stability issues and performance were not fully under- stood and were still being worked out during the early phases of the project. Agile methodology resolved this issue with the team significantly altering the third and fourth sprints to focus around these customer issues, allowing new features to be put in front of other planned features from the backlog. The Agile method was responsible for both uncovering and resolving this challenge. Agile Benefits For complex projects Agile methodology offers numerous benefits to the software development team and the customer commissioning the creation of the software. Improved control Users create wish lists of requests that Customer gathers and high grades. Customer directs what features are put into development. Customer prioritizes feature enhancements. Customer adds or deletes features from product backlog as priorities change. Customer participates in daily scrum to monitor progress, obstacles, risks, and changes. Customer receives working product at end of each sprint to inspect and deploy. Faster results Working software results from every sprint. The most critical features are delivered first. Numerous, small, reversible decisions are made quickly, keeping team moving forward. Higher quality Quality is incorporated at each iteration, not bolted on at the end. Feedback is closer to real-time Less waste Unnecessary features are eliminated early. Less time is wasted finding people and information. Scope creep is replaced by flexible development that is responsive to ongoing changes. Reduced time is spent producing dead documents in favor of living artifacts. Release process is simplified (i.e. testing, coding, PM, release engineering, etc.) Better product Frequent, structured communication with Product Owner means the end result is closer to customer vision. Change is welcome, so finished product incorporates ideas that arise after development launches. Developers are free to think creatively throughout the project, which yields better solutions.
8 Lower risk The process ferrets out failure early before a lot of effort is invested. Risks are brought forward rather than delayed reducing the cost of making adjustments. Complexity is mitigated by breaking down large efforts into simpler mini-projects called sprints. Early and regular process improvement and course correction occurs through frequent inspection. Risk Seriousness Inception Waterfall Iterative Waterfall Integration & Test Period Elaboration Construction Time Requirements Design Implementation Testing Reduced cost Customer invests only in features that are valuable because the Product Owner is involved in the daily Scrum Meetings. Quick delivery cycles allow client to capture value early to offset project cost. Waste reduction reduces time spent on low value activities. Fail early, fail often reduces costs of errors.
Agile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationAgile Project Management By Mark C. Layton
Agile Project Management By Mark C. Layton Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products. Agile project management
More informationHow To Understand The Limitations Of An Agile Software Development
A Cynical View on Agile Software Development from the Perspective of a new Small-Scale Software Industry Apoorva Mishra Computer Science & Engineering C.S.I.T, Durg, India Deepty Dubey Computer Science
More informationAGILE METHODOLOGY IN SOFTWARE DEVELOPMENT
AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT Shivangi Shandilya, Surekha Sangwan, Ritu Yadav Dept. of Computer Science Engineering Dronacharya College Of Engineering, Gurgaon Abstract- Looking at the software
More informationProcess Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
More informationPROCESS OF MOVING FROM WATERFALL TO AGILE PROJECT MANAGEMENT MODEL
PROCESS OF MOVING FROM WATERFALL TO AGILE PROJECT MANAGEMENT MODEL Sanja Vukićević 1, Dražen Drašković 2 1 Faculty of Organizational Sciences, University of Belgrade, vukicevicsanja@yahoo.com 2 Faculty
More informationLife Cycle Models. V. Paúl Pauca. CSC 331-631 Fall 2013. Department of Computer Science Wake Forest University. Object Oriented Software Engineering
Life Cycle Models V. Paúl Pauca Department of Computer Science Wake Forest University CSC 331-631 Fall 2013 Software Life Cycle The overall framework in which software is conceived, developed, and maintained.
More informationAgile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
More informationAgile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield
Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise:
More informationThe Basics of Scrum An introduction to the framework
The Basics of Scrum An introduction to the framework Introduction Scrum, the most widely practiced Agile process, has been successfully used in software development for the last 20 years. While Scrum has
More informationAgile Project Management A Primer. Brian Stewart AVU ACEP Nairobi 17 th 2013
Agile Project Management A Primer Brian Stewart AVU ACEP Nairobi 17 th 2013 http://www.coleyconsulting.co.uk/images/waterfall-model.gif Problems with waterfall model Over-planning Insufficient Communication
More informationThe Agile Manifesto is based on 12 principles:
The Agile Manifesto is based on 12 principles: Customer satisfaction by rapid delivery of a useful product solution Welcome changing requirements, even late in development Working products are delivered
More informationwww.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Created by Stephen Barkar - www.stephenbarkar.se
1 www.stephenbarkar.se Lean vs. Agile similarities and differences 2014-08-29 Purpose with the material 2 This material describes the basics of Agile and Lean and the similarities and differences between
More informationAgile Development Overview
Presented by Jennifer Bleen, PMP Project Services Practice of Cardinal Solutions Group, Inc. Contact: Agile Manifesto We are uncovering better ways of developing software by doing it and helping others
More informationA Viable Systems Engineering Approach. Presented by: Dick Carlson (richard.carlson2@boeing.com)
A Viable Systems Engineering Approach Presented by: Dick Carlson (richard.carlson2@boeing.com) Philip Matuzic (philip.j.matuzic@boeing.com) i i Introduction This presentation ti addresses systems engineering
More informationLEAN AGILE POCKET GUIDE
SATORI CONSULTING LEAN AGILE POCKET GUIDE Software Product Development Methodology Reference Guide PURPOSE This pocket guide serves as a reference to a family of lean agile software development methodologies
More informationAGILE - QUICK GUIDE AGILE - PRIMER
AGILE - QUICK GUIDE http://www.tutorialspoint.com/agile/agile_quick_guide.htm Copyright tutorialspoint.com AGILE - PRIMER Agile is a software development methodology to build a software incrementally using
More informationAgile Software Development in the Large
Agile Software Development in the Large Jutta Eckstein 1 Large Large in... Scope Time People Money Risks We concentrate on Large Teams Large is relative 1, 2, 10, 100, 2000 People 2 Principles behind Agile
More informationCOMP 354 Introduction to Software Engineering
COMP 354 Introduction to Software Engineering Greg Butler Office: EV 3.219 Computer Science and Software Engineering Concordia University, Montreal, Canada Email: gregb@cs.concordia.ca Winter 2015 Course
More informationScrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014
Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014 1 Goals Cover Material from our User Stories Book Chapter 15: Using Stories With Scrum Chapter 16: Additional
More informationThis handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people:
AGILE HANDBOOK OVERVIEW WHAT IS THIS? This handbook is meant to be a quick-starter guide to Agile Project Management. It is meant for the following people: Someone who is looking for a quick overview on
More informationAgile Software Development. Mohsen Afsharchi
Agile Software Development Mohsen Afsharchi I. Agile Software Development Agile software development is a group of software development methods based on iterative and incremental development, where requirements
More informationThe style is: a statement or question followed by four options. In each case only one option is correct.
AGILE FOUNDATION CERTIFICATE SAMPLE FOUNDATION QUESTIONS WITH ANSWERS This document is a set of sample questions, in the style of the Agile Foundation Certificate Examination, which is a 60 question, 1
More informationAdapting Agile Software Development to Regulated Industry. Paul Buckley Section 706 Section Event June 16, 2015
Adapting Agile Software Development to Regulated Industry Paul Buckley Section 706 Section Event June 16, 2015 Agenda FDA s expectations for Software Development What is Agile development? Aligning Agile
More informationAgile-Waterfall Hybrid Jessica LaGoy, MS, PMP
Agile-Waterfall Hybrid Jessica LaGoy, MS, PMP About Jess BS Applied Physics, WPI / MS Cybersecurity, UMUC PMP, ITIL, Data Scientist, Tableau, Alteryx Project Experience Data and technology Construction
More information2015 Defense Health Information Technology Symposium Implementation of Agile SCRUM Software Development Methodology
Mr. Christopher Harrington, PM Clinical Support, Solution Delivery Division Mr. James Huber, Healthcare Data Analyst, DHA Decision Support 2015 Defense Health Information Technology Symposium Implementation
More informationAgile Project. Management FOR DUMME&* by Mark C. Layton WILEY. John Wiley & Sons, Inc.
Agile Project Management FOR DUMME&* by Mark C. Layton WILEY John Wiley & Sons, Inc. Table of Contents»#» « Introduction / About This Book 1 Foolish Assumptions 1 Conventions Used in This Book 2 How This
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationGovernments information technology
So l u t i o n s Blending Agile and Lean Thinking for More Efficient IT Development By Harry Kenworthy Agile development and Lean management can lead to more cost-effective, timely production of information
More informationRole of Agile Methodology in Software Development
Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology IJCSMC, Vol. 2, Issue. 10, October 2013,
More informationCase Study on Critical Success Factors of Running Scrum *
Journal of Software Engineering and Applications, 2013, 6, 59-64 http://dx.doi.org/10.4236/jsea.2013.62010 Published Online February 2013 (http://www.scirp.org/journal/jsea) 59 Case Study on Critical Success
More informationAgile Project Management with Scrum
Agile Project Management with Scrum Resource links http://www.agilealliance.org/ http://www.agilemanifesto.org/ http://www.scrum-master.com/ 1 Manifesto for Agile Software Development Individuals and interactions
More informationSCRUM BODY OF KNOWLEDGE (SBOK Guide)
A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK Guide) 2013 Edition A Comprehensive Guide to Deliver Projects using Scrum TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 Overview of Scrum...
More informationWhat is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process
What is Scrum? From http://www.scrumalliance.org/pages/what_is_scrum A lean approach to software development Scrum is an agile software development framework. Work is structured in cycles of work called
More informationAgile Methodologies and Its Processes
International Journal of Computational Engineering Research Vol, 03 Issue, 9 Agile Methodologies and Its Processes 1, Akanksha, 2, Akansha Rakheja, 3, Latika Kapur, 4, Kanika Ahuja 1,2,3,, Information
More informationSometimes: 16 % Often: 13 % Always: 7 %
SCRUM AT RIIS A Standish study found that only 20% of features in a typical system were used often or always and 45% of features were never used at all. The ability to embrace change is critical to reducing
More informationProduct Development: From Conception to Execution. Slide 1
Product Development: From Conception to Execution Slide 1 Product Development: From Conception to Execution Becky Lester, CPCU GAINWeb Product Owner Grange Insurance Damon Lay, ACAS, MAAA Director Business
More informationD25-2. Agile and Scrum Introduction
D25-2 Agile and Scrum Introduction How to Use this Download This download is an overview of a discussion Intertech has with clients on Agile/Scrum This download has an overview of Agile, an overview of
More informationAgile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
More informationTransitioning from Waterfall to Agile Course AG01; 3 Days, Instructor-led
Transitioning from Waterfall to Agile Course AG01; 3 Days, Instructor-led Course Description Identify the challenges you will face when implementing an Agile approach to software development and then plan
More information10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design
Session # 3 Contents Systems Analysis and Design 2 1 Tiers of Software Development 10/4/2013 Information system development project Realistic behavior 3 Information system development project System Development
More informationAn Agile Project Management Model
Agile Project Management Jim Highsmith Chapter 5 An Agile Project Management Model We improve effectiveness and reliability through situationally specific strategies, processes, and practices. One of the
More informationSoftware Development Methodologies
Software Development Methodologies Jonathan Hoyle Eastman Kodak Thursday, June 2, 2005 Overview Predictive Methodologies Waterfall Other Predictive Methodologies Agile Methodologies Extreme Programming
More informationHow to manage agile development? Rose Pruyne Jack Reed
How to manage agile development? Rose Pruyne Jack Reed What will we cover? Introductions Overview and principles User story exercise Retrospective exercise Getting started Q&A About me: Jack Reed Geospatial
More informationSCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON
SCRUM A Tool from the Software World Can Improve Analytical Project Outcomes By KyMBER WALTMUNSON When jurisdictions undertake analytical work such as audits, budget analysis, program evaluation, and special
More informationTransitioning from Waterfall: The Benefits of Becoming Agile. ASPE Web Seminar Friday, February 27 th, 2015
Transitioning from Waterfall: The Benefits of Becoming Agile ASPE Web Seminar Friday, February 27 th, 2015 Objectives Give a high-level look at the challenges in software development Give a basic look
More informationCertified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Each percentage
More informationInformation Management for National Guard Agribusiness Development Teams: An Agile Development Case Study
Information Management for National Guard Agribusiness Development Teams: An Agile Development Case Study Authors: Lynndee Kemmet, Network Science Center at West Point; Ray McGowan, Army CERDEC; C. Reed
More informationAgile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 4 Scrum: Current Framework 1 Scrum: New Process Framework 1. A people-centric framework based on a set of values, principles, and practices that
More informationCertified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012 The following pages present the CSM taxonomy as validated through the 2011 Scrum Alliance Validation Study. Total questions
More informationAlternative Development Methodologies
Alternative Development Methodologies The Software Development Process described in the course notes and lecture is a generalized process that been in use for decades. Over this time, scholars in the IT
More informationAgile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering. Shvetha Soundararajan
Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering Shvetha Soundararajan Thesis submitted to the faculty of the Virginia Polytechnic Institute and State University
More informationChapter 6. Iteration 0: Preparing for the First Iteration
Chapter 6. Iteration 0: Preparing for the First Iteration People only see what they are prepared to see. Ralph Waldo Emerson There are no secrets to success. It is the result of preparation, hard work,
More informationWaterfall to Agile. DFI Case Study By Nick Van, PMP
Waterfall to Agile DFI Case Study By Nick Van, PMP DFI Case Study Waterfall Agile DFI and Waterfall Choosing Agile Managing Change Lessons Learned, Sprints Summary Q and A Waterfall Waterfall Waterfall
More informationAgile Project Management
Agile Project Management Projekt-Kick-Off-Tage Hochschule Augsburg Martin Wagner, 15. März 2011 TNG Technology Consulting GmbH, http://www.tngtech.com Agile project management with Scrum Agenda Software
More informationThe Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July 2013. Developed and sustained by Ken Schwaber and Jeff Sutherland
The Scrum Guide The Definitive Guide to Scrum: The Rules of the Game July 2013 Developed and sustained by Ken Schwaber and Jeff Sutherland Table of Contents Purpose of the Scrum Guide... 3 Definition of
More informationProject Management in Software: Origin of Agile
PAGE 1 ios App Development Project Management in Software: Origin of Agile PAGE 2 Learning Outcomes By the end of the unit, you should be able to: 1. Differentiate between Waterfall and Agile process 2.
More informationBottlenecks in Agile Software Development Identified Using Theory of Constraints (TOC) Principles
Master thesis in Applied Information Technology REPORT NO. 2008:014 ISSN: 1651-4769 Department of Applied Information Technology or Department of Computer Science Bottlenecks in Agile Software Development
More informationAgile Software Development Methodologies and Its Quality Assurance
Agile Software Development Methodologies and Its Quality Assurance Aslin Jenila.P.S Assistant Professor, Hindustan University, Chennai Abstract: Agility, with regard to software development, can be expressed
More informationDevelopment. Lecture 3
Software Process in Modern Software Development Lecture 3 Software Engineering i Practice Software engineering practice is a broad array of principles, concepts, methods, and tools that must be considered
More informationSoftware Engineering
1 Software Engineering Lecture 2: Software Life Cycles Stefan Hallerstede Århus School of Engineering 25 August 2011 2 Contents Naive Software Development Code & Fix Towards A Software Process Software
More informationAgile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 24.01.2013 1 Application development lifecycle model To support the planning and management of activities required in
More informationIntroduction to Agile
Chapter 1 Introduction to Agile Objectives: Define Agile software development Explain differences and similarities between various lightweight methodologies Learn the core principles of Agile Dispel common
More informationCourse Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
More informationNeglecting Agile Principles and Practices: A Case Study
Neglecting Agile Principles and Practices: A Case Study Patrícia Vilain Departament de Informatics and Statistics (INE) Federal University of Santa Catarina Florianópolis, Brazil vilain@inf.ufsc.br Alexandre
More informationThe Truth About Agile Software Development with Scrum, The Facts You Should Know
The Truth About Agile Software Development with Scrum, The Facts You Should Know Copyright Notice of rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any
More informationCSE 435 Software Engineering. Sept 16, 2015
CSE 435 Software Engineering Sept 16, 2015 2.1 The Meaning of Process A process: a series of steps involving activities, constraints, and resources that produce an intended output of some kind A process
More informationIntroduction to Scrum
Introduction to Scrum Recorded by Michael James [Existing slide with MJ] Welcome to Module 1 of CollabNet s Scrum Training Series: Introduction to Scrum. This is a brief introduction to topics that are
More informationSCRUM 1. Upon what type of process control is Scrum based? a. Empirical b. Hybrid c. Defined d. Complex
SCRUM 1. Upon what type of process control is Scrum based? a. Empirical b. Hybrid c. Defined d. Complex 2. The three pillars of empirical process control are: a. Respect for People, Kaizen, Eliminating
More informationBusiness Analysts in an Agile World. Christian Antoine
Business Analysts in an Agile World Christian Antoine What is this about Value of software Building the right product Building the product right Where do BA s fit in this What this is not Back to basics
More informationCSPO Learning Objectives Preamble. Scrum Basics
CSPO Learning Objectives Preamble This document contains topics for the Certified Scrum Product Owner (CSPO) training course. The purpose of this document is to describe the minimum set of concepts and
More informationPractical Agile Requirements Engineering
Defense, Space & Security Lean-Agile Software Practical Agile Requirements Engineering Presented to the 13 th Annual Systems Engineering Conference 10/25/2010 10/28/2010 Hyatt Regency Mission Bay, San
More informationAn Introduction to Agile Performance Management
! 1 An Introduction to Agile Performance Management by Jeffrey B. Rothman, Ph.D. An Introduction to Agile This is a high level introduction to Agile -- a well known productivity framework for software
More informationWhy Agile Works: Economics, Psychology, and Science. @MatthewRenze #PrDC16
Why Agile Works: Economics, Psychology, and Science @MatthewRenze #PrDC16 Purpose Explain why Agile practices are so successful Insights from: Economics Psychology Science Top 7 most important ideas Ideas
More informationHow To Write A Thesis On How To Create And Maintain Documentation In An Agile Development Environment
}w!"#$%&'()+,-./012345
More informationLean Software Development and Kanban
1 of 7 10.04.2013 21:30 Lean Software Development and Kanban Learning Objectives After completing this topic, you should be able to recognize the seven principles of lean software development identify
More informationLean QA: The Agile Way. Chris Lawson, Quality Manager
Lean QA: The Agile Way Chris Lawson, Quality Manager The Quality Problem Agile Overview Manifesto Development Methodologies Process Agile QA Lean QA Principles An Agile QA Framework Summary Q & A Agenda
More informationSoftware Requirements and Specification
Software Requirements and Specification Agile Methods SE3821 - Jay Urbain Credits: Beck, K. (1999). Extreme Programming Explained: Embrace Change. Boston, MA: Addison-Wesley. Beck, Kent; et al. (2001).
More informationSoftware Development Life Cycle
4 Software Development Life Cycle M MAJOR A J O R T TOPICSO P I C S Objectives... 52 Pre-Test Questions... 52 Introduction... 53 Software Development Life Cycle Model... 53 Waterfall Life Cycle Model...
More informationUSCIS/SPAS: Product Backlog Items and User Stories 4/16/2015. Dr. Patrick McConnell
USCIS/SPAS: Product Backlog Items and User Stories 4/16/2015 Dr. Patrick McConnell July 9, 2015 1 First, an old joke.. I can t identify an original source for this cartoon. As best as I can tell, the art
More informationStrategic View on Various Sub-paradigms of Agile Methodology and Sig Sigma Approach
International Journal of Information and Computation Technology. ISSN 0974-2239 Volume 3, Number 3 (2013), pp. 153-162 International Research Publications House http://www. irphouse.com /ijict.htm Strategic
More informationMitigating Risk with Agile Development. Rich Mironov CMO, Enthiosys
Mitigating Risk with Agile Development Rich Mironov CMO, Enthiosys 2 About Rich Mironov CMO at Enthiosys, agile product mgmt consultancy Business models/pricing, roadmaps Agile transformation and Interim
More informationAgile and lean methods for managing application development process
Agile and lean methods for managing application development process Hannu Markkanen 27.01.2012 1 Lifecycle model To support the planning and management of activities required in the production of e.g.
More informationWho Doesn t Want to be Agile? By: Steve Dine President, Datasource Consulting, LLC 7/10/2008
Who Doesn t Want to be Agile? By: Steve Dine President, Datasource Consulting, LLC 7/10/2008 Who wants to be involved in a BI project or program that is labeled slow or inflexible? While I don t believe
More informationIntroduction to Agile Scrum
Introduction to Agile Scrum by Julia M. Lobur Penn State Harrisburg CMPSC 487W Fall 2015 Introduction to Scrum Learning Goals Relationship of Scrum to other Agile methods Scrum Framework Scrum Roles Scrum
More informationRISK MANAGMENT ON AN AGILE PROJECT
BIO PRESENTATION W3 6/28/ 11:30 AM RISK MANAGMENT ON AN AGILE PROJECT Michele Sliger Rally Software Development Better Software Conference June 26 29, Las Vegas, NV USA Michele Sliger Michele Sliger has
More informationQuality Assurance in an Agile Environment
Quality Assurance in an Agile Environment 1 Discussion Topic The Agile Movement Transition of QA practice and methods to Agile from Traditional Scrum and QA Recap Open Discussion www.emids.com 2 What is
More informationFrank Cervone Vice Chancellor for Information Services and Chief Information Officer Purdue University Calumet January 17, 2012 CARLI Anatomy of a
Frank Cervone Vice Chancellor for Information Services and Chief Information Officer Purdue University Calumet January 17, 2012 CARLI Anatomy of a Digital Project webinar series An overview and background
More informationAgile Software Development
Agile Software Development Application in the Medical Device Industry Kelly Weyrauch Medtronic, Inc. (29 April 2008) Introduction Purpose Provide an introduction to Agile Software Development as it applies
More informationOne Trusted Platform. For all your software projects. Agile. Integrated. Simplified. Requirements brought to you the most
Agile. Integrated. Simplified One Trusted Platform For all your software projects Requirements Innoeye Technologies brought to you the most Defects and Change Requests Test planning / execution Iterations
More informationSoftware Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
More informationAgile Requirements Definition and Management (RDM) How Agile requirements help drive better results
Thought Leadership: Requirements Definition and Management Agile Requirements Definition and Management (RDM) How Agile requirements help drive better results Jason Moccia One of the myths of Agile software
More informationAgile & Scrum: What are these methodologies and how will they impact QA/testing roles? Marina Gil Santamaria Summer 2007
Agile & Scrum: What are these methodologies and how will they impact QA/testing roles? Marina Gil Santamaria Summer 2007 The idea behind the Agile approach is that instead of building a release that is
More informationAgile Software Development in the Large
Agile Software Development in the Large GI-Vortrag Braunschweig Jutta Eckstein Nicolai Josuttis What Does Large Mean? Large in... scope time people money risks We focus on Large Teams which implies everything
More informationIMPLEMENTING SCRUM. PART 1 of 5: KEYS TO SUCCESSFUL CHANGE
IMPLEMENTING SCRUM GUIDE PART 1 of 5: KEYS TO SUCCESSFUL CHANGE Created by Axosoft, makers of the #1 Scrum software, in collaboration with writer and coach, Tirrell Payton. A STORY ABOUT NIC AND SKIP I
More informationABHINAV NATIONAL MONTHLY REFEREED JOURNAL OF RESEARCH IN SCIENCE & TECHNOLOGY www.abhinavjournal.com
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) ANALYTICAL COMPARISON AND SURVEY ON TRADITIONAL AND AGILE METHODOLOGY Sujit Kumar Dora 1 and Pushkar Dubey 2 1 Programmer, Computer Science & Engineering, Padmashree
More informationAdopting Agile Project Management - Corporate Culture Must Match (Apr 15)
Adopting Agile Project Management - Corporate Culture Must Match (Apr 15) by Megan Torrance April 20, 2015 If you re contemplating adopting an agile approach, and the thought of implementing new project
More informationGénie Logiciel et Gestion de Projets. Software Processes Focus on Extreme Programming
Génie Logiciel et Gestion de Projets Software Processes Focus on Extreme Programming 1 Roadmap Process, Method, Methodology?? What is a software process? Software Process Models Methodologies: RUP Focus
More informationTraditional requirements
What do we do now? Traditional requirements Reams of paper Detailed requirements documented upfront Documentation of so many requirements that they had to be identified as mandatory or desirable Customers
More informationLasting commercial success with Agile Evolution
Turning visions into business December 2011 Lasting commercial success with Agile Evolution Malte Foegen, David Croome, Timo Foegen Scrum techniques are spreading increasingly. In many cases, they lead
More information