Managing Agile, Waterfall and Hybrid projects within the Portfolio

Slides:



Advertisements
Similar presentations
Basic SDLC Models.
Advertisements

Facilitated by Joanne Fraser RiverSystems
Internet Librarian 2007 Project management workshop 28 th October 2007 Mary Auckland Project management workshop 28 th October.
SharePoint Project Management. EPM Live provides Microsoft-Base Project Management solutions that allow individuals, teams, workgroups, and organizations.
Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Basic Project Planning and Estimation 2/5/2007 Keith Rome
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Agile development By Sam Chamberlain. First a bit of history..
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Software Engineering.
What is a project? Project Management Institute definition
CHAPTER 9: LEARNING OUTCOMES
1 Agile Estimating and Planning October, 2013 Technion, Israel Prof. Fabio Kon University of Sao Paulo, Brazil
Next Generation Trnsport Trnsport Users Group Conference Field Management TAG November 7, 2005.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Project Planning & Estimating – Are we there yet?
CSI315 Web Technology and Applications
Software Project Management Introduction to Project Management.
Chapter 11 McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
Agile Software Development Brian Link
Lifecycle Management and the Projects Portfolio. 2 Agenda How project portfolio management fits within an overall lifecycle for managing the delivery.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Industrial Software Project Management Some views on project managing industrial and business software projects.
Best of Both Worlds: Information Management Solutions SmartCore Management Dashboards.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Agile Project Management. An Informed Decision It is not a snap decision whether to use an agile approach or not, just like flying or driving somewhere.
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin CHAPTER NINE SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT CHAPTER.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Introduction to Project Management.  Explain what a project is?  Describe project management.  Understand project management framework.  Discuss the.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Tools and Techniques for Project Portfolio Management Jon Lewis - Director, Ninth Wave.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Project management methodologies Waterfall vs. agile vs. half-arsed agile.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1. ENTERPRISE AGILE TRANSFORMATION AT THE US POSTAL SERVICE MAY 24, Agile Business Solutions.
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
 Son Nguyen, YM & Skype: ng_thanhson.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Managing Software Development Projects with Jira.
CHAPTER 9: LEARNING OUTCOMES
PA Techcon: Project management
Strategic Information Systems Planning
Start End What is a project? Definition from PMBOK -
Appendix B Agile Methodologies
Introduction and background
Chapter 3: The Project Management Process Groups: A Case Study
Introduction to Software Engineering
Agile Delivery Process Improvement
Practical Software Engineering
Tudorel Pavel Valentina Filip
Teaching slides Chapter 13
Presentation transcript:

Managing Agile, Waterfall and Hybrid projects within the Portfolio Jon Lewis - Director, Ninth Wave

Agenda Introducing agile management techniques alongside traditional waterfall based planning is becoming increasingly important for many of our customers. In this session, we’ll describe and explain some of the issues in managing a mix of waterfall projects, fully Agile projects and projects following a hybrid agile/ waterfall approach, all within the same project portfolio. We’ll share Ninth Wave’s ideas and experience in this area and show some of the tools and techniques that we use to support project portfolio management with these different project approaches.  

Project Types Waterfall: Agile development: Plan Build Review Test   Plan Build Review Test Deploy Plan Build Review Test Deploy

Hybrid Project Types Iterative Waterfall: Continuous Agile development:   Plan Build Review Test Deploy Plan Build Review Test Deploy Plan Build Review Test Deploy

Waterfall: Requirements are known and fixed at the outset Changes can be expensive or impossible Different skills and resources are needed at different times Delays in one area have a knock on effect Testing is towards the end of the project The end date and cost are not ‘fixed’ Benefits typically not realised until the end Plan Build Review Test Deploy

Agile Development: Requirements don’t all have to be fixed at the outset Developments are time-boxed Focus is on delivering sets of independent features Changes can be incorporated at a later stage Resources used more efficiently Slippage is much more obvious Delays in one area not as critical The end date can be fixed.. ..by deployment of what has been signed off at a given time. Plan Build Review Test Deploy

Iterative Waterfall: A larger project broken down into phases Only some requirements fixed at the outset Changes can be incorporated in a later phase Resource use not efficient within the project Delays in one area affect deployment of current and later phases The end dates can slip and costs can rise Benefits can be realised from delivery of phase 1 Plan Build Review Test Deploy Plan Build Review Test Deploy

Continuous Agile Development: Requirements don’t have to be fixed at the outset Changes can be incorporated at any later stage Resources used efficiently Nothing is done until it is needed Delays in one area not critical Multiple small deployments at fixed dates Benefits can be realised very quickly (self funding?) But this could result in training and change management issues. Plan Build Review Test Deploy

Tools and techniques available: Waterfall: Estimation tools Project planning and tracking Financial management and time recording Resource management Deliverable management and governance Plan Build Review Test Deploy

Project Planning/ Gantt:

Project Financials:

Documents and Governance:

Tools and techniques available: Agile: Planning poker Sprint and burndown chart Scrum/ Kanban board Build/ release management Plan Build Review Test Deploy

Sprint and Burndown Chart:

Scrum/ Kanban Board:

Cards based work allocation:

In-task time recording:

Build/ Release Management:

Managing different project types in the portfolio: As we’ve just seen, Agile, Waterfall and Hybrid projects will all need to be managed in slightly different ways in terms of: Project definition and scoping Planning and resourcing Financial management Governance Tracking and reporting Plan Build Review Test Deploy Plan Build Review Test Deploy Plan Build Review Test Deploy

The Iron Triangle: Quality Time Cost Scope Good project management requires delivery within the triple constraints of time, cost and scope and to the desired quality: Good project portfolio management requires delivery across the portfolio within overall triple constraints of time, cost and scope, whilst achieving the level of quality required. Quality Time Cost Scope

The Iron Triangle (II): Agile projects are typically driven to meeting specific delivery dates with given resources and delivering as much as possible within those constraints. The Iron Triangle (II): Waterfall projects are typically driven to achieving a fixed scope and measured on delivery vs. plan and cost vs. budget: Quality Quality TRACK Time CONTROL Cost FIXED Time FIXED Cost FIXED Scope VARIABLE Scope

Measuring performance across the portfolio: Report a range of RAGs or statuses - for Delivery, Costs, Benefits and Risks and Issues to highlight problem areas regardless of the type of project:

Ninth Wave and SmartCore Ninth Wave is an independent UK-based software and services firm established in 1995 Our main software product is SmartCore, a proven web-based management support tool The product has been developed from practical experience of project and programme management SmartCore is unique - it is entirely configurable via the web browser to meet a wide range of organisational and individual information needs.  

SmartCore - Major Functional Components Strategic Alignment Portfolio Management Governance/ Change Management Budgets & Financial Management Programme & Project Management Resource Management Risk & Issue Management Workflow & Business Rules Timesheets Benefits Management Document Management Dashboards & Reporting

SmartCore Customers:

Timebox 1 Complete End of Presentation

Project Portfolio Management SmartCore 0207 403 4433 jon.lewis@ninthwave.co.uk www.ninthwave.co.uk Project Portfolio Management from Ninth Wave