CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

Walter Bodwell Planigle. An Introduction – Walter Bodwell First did agile at a startup in 1999 Got acquired by BMC in 2000 and spent the next 8 years.
Prescriptive Process models
2003 Mateusz Żochowski, Marcin Borzymek Software Life Cycle Analysis.
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Software Process Models
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Alternate Software Development Methodologies
Dynamic Systems Development Method (DSDM)
Software Engineering.
Object-oriented Analysis and Design
Chapter 5: Project Scope Management
Iterative development and The Unified process
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 5: Project Scope Management
Systems Analysis and Design. Systems Development Life Cycle (SDLC) Systems Analysis Systems Design Programming Testing Conversion On-going maintenance.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
CSE Senior Design I Risk Management Instructor: Mike O’Dell This presentations was derived from the textbook used for this class: McConnell, Steve, Rapid.
Project Scope Management
Release & Deployment ITIL Version 3
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 CSE 403 Software Lifecycle Models Reading: Rapid Development Ch. 7, 25 (further reading: Ch. 21, 35, 36, 20) These lecture slides are copyright (C) Marty.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
When is Agile the Best Project Management Method? Lana Tylka.
Software Development Process and Management (or how to be officious and unpopular)
VCU Information Systems Institute Advanced Delivery Methodology Courtesy of Data Management That Works.
CSE Senior Design I Building a Plan Instructor: Vassilis Athitsos Several of the slides in this module are a modification and amplification of slides prepared.
CSE Senior Design I Building a Plan Instructor: Mike O’Dell Several of the slides in this module are a modification and amplification of slides prepared.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Project Tracking Why and How to Do It. The Dilbert View.
Software Engineering MCS-2 Lecture # 6
The Long Tail Why the future of business is selling less of more ▫ISBN = ▫Chris Anderson Low Distribution and Inventory costs allow companies.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
CSE Senior Design II Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Development Life Cycle (SDLC)
Establishing Project Scope 1. Factors Affecting Project Scope  The functionality that must be delivered to meet the user’s needs  The resources available.
CSE 403, Spring 2008, Alverson Software Development Lifecycle The Power of Process.
CSE Senior Design II Timebox Development Mike O’Dell Based on an earlier presentation by Bill Farrior, UTA, modified by Mike O’Dell.
Software Lifecycle Models A software lifecycle model is a standardised format for planning organising, and running a new development project.
44222: Information Systems Development
Timebox Development Mike O’Dell Based on an earlier presentation by
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Software Lifecycle Models Place of Testing in Software Lifecycle 1.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Project Management Software development models & methodologies
TK2023 Object-Oriented Software Engineering
Managing the Project Lifecycle
Mike Cohn - Agile Estimating and Planning
Information Technology Project Management – Fifth Edition
How to Successfully Implement an Agile Project
Lecture 02: Software Lifecycle Models
Timebox Development Instructor: Manfred Huber
Lecture 03: Software Lifecycle Models
Presentation transcript:

CSE Senior Design II Staged Delivery Instructor: Mike O’Dell

1 CSE What is Staged Delivery? Requirements Analysis Concept & Planning Architectural Design Medium High Priority: Detailed design, implement and test Medium Priority: Detailed design, implement and test High Priority: Detailed design, implement and test Medium Low Priority: Detailed design, implement and test Low Priority: Detailed design, implement and test Run out of time and/or money Public Release Design-to-Schedule with risk reduction.

1 CSE What is Staged Delivery?  A Lifecycle Model in which the: discrete stages  product is designed (details), developed and delivered in discrete stages prioritized,  requirements are clearly prioritized, and consistent with implementation dependencies  schedule determines  schedule determines the features that are delivered at each stage  the deliverable at any stage is “completed” potentially “shippable”

1 CSE Why Consider Staged Delivery?  Staged Delivery can, potentially: reduce risk  significantly reduce risk associated with an “all or nothing” release signs of progress  provide clear signs of progress toward the ultimate product definition  improve product quality build-to-budget  facilitate a build-to-budget project team morale  help maintain team morale during the end game

1 CSE Requirements for Staged Delivery product requirements  Clear and agreed statement of product requirements prioritization  Buy-in at all levels on prioritization of features/requirements  AND staging of deliverables stakeholders and end-users  Willingness of stakeholders and end-users to accept less than “the whole enchilada”

1 CSE Requirements for Staged Delivery partition the deliverables  Ability to partition the deliverables into phased releases (stages) focus on quality  Commitment to focus on quality of each staged release architectural model  A clear and well-defined architectural model, precisely mapped to your requirements.

1 CSE Advantages of Staged Delivery  Provides visible signs of progress for customers and stakeholders mitigates “90-90”  obviates, mitigates “90-90” rule predictable releases  Allows frequent and predictable releases  internal or external Beta  internal or external Beta releases/customer testing? frequent customer/end- user feedback  encourages early and frequent customer/end- user feedback marketing and sales team  engages marketing and sales team in process

1 CSE Advantages of Staged Delivery early warning  Provides early warning of problems in development  Ability/Inability to deliver core features and functionality will be clear well before deadline.  Cuts down on project management overhead  less reporting… more frequent delivering! release options  Increases release options  e.g., release version 1, hold version 2, release version 3, …

1 CSE Advantages of Staged Delivery estimation error  Reduces estimation error  smaller tasks to estimate -> less variance integration and test  Reduces integration and test effort But…

1 CSE Major Risk with Staged Delivery Feature Creep, late in the game!

1 CSE Keys to Success with Staged Delivery architecture is flexible  Be sure that the product architecture is flexible, supporting as many future directions as possible importance/priority  Plan stages in order of importance/priority first stage as early as possible  Define the first stage so that it can be delivered as early as possible themes  Define the stages in terms of “themes” stakeholder buy-in  Get stakeholder buy-in on staging plan  Tightly control/manage feature set

1 CSE Keys for Senior Design Projects at least 3 or 4 stages  Define at least 3 or 4 stages for your delivery one week prior to “Early Prototype Preview”  Suggest timing your first stage (core functionality which support further development) to occur at least one week prior to “Early Prototype Preview” date interim release (stage)  One more interim release (stage) one week before Final Presentations.  Final stage completed 1-2 days before  Final stage completed 1-2 days before Final Presentations.