Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Slides:



Advertisements
Similar presentations
Requirements Specification and Management
Advertisements

BUSINESS DRIVEN TECHNOLOGY
CSSE October.2008 APF wrap-up and xPM Chapter
INFO 638Lecture #81 Software Project Management Cycle plan and build INFO 638 Glenn Booker.
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
1 Human-Centered Design I Presented by: Craig Titus EPICS High Workshop – Summer 2010 Lecture: Human-Centered Design Presented By: Craig Titus.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Quality is about testing early and testing often Joe Apuzzo, Ngozi Nwana, Sweety Varghese Student/Faculty Research Day CSIS Pace University May 6th, 2005.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Iterative development and The Unified process
Chapter 3: The Project Management Process Groups
Introduction to Systems Analysis and Design
CHAPTER 19 Building Software.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
Advanced Project Management Project Plan Templates
Prof. Roy Levow Session 12.  Introduction to Project Portfolio Management  Establishing a Portfolio Strategy  Evaluating Project Alignment to the Portfolio.
Project Management Process Overview
S/W Project Management
Prof. Roy Levow Sessions 3.  Clear statement of what the project is about  Necessary for traditional project management  Deliverable is one-page Project.
Chapter 5 System Analysis Sarah El Sehemawy Karim Elsabee Sherine Meshad Hakim Meshriky Ahmed Zaki Ismail Abou Hamda.
Chapter 2 The process Process, Methods, and Tools
Research Project Management Mostafa Lotfi,PMP,MCTS 2011/6/15.
Effective Complex Project Management
5.1 Principles of Project Management. So what is Project Management? Definition: Is the process of planning, organizing, and managing tasks and resources.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Prof. Roy Levow Session 9.  Defining the APF  An Overview of the APF  The APF Core Values.
Chapter 14 Information System Development
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
Successful IT Projects slides © 2007 Darren Dalcher & Lindsey Brodie Successful IT Projects By Darren Dalcher & Lindsey Brodie
Prof. Roy Levow Session 8.  Steps in Closing a Project  Getting Client Acceptance  Installing Project Deliverables  Documenting the Project  Post-Implementation.
Chapter 5 Defining and Managing Project and Product Scope Copyright 2012 John Wiley & Sons, Inc. 5-1.
Task: Copyright © 2003 PM tec, Inc; D. Sankey; D. Padelford. All rights reserved. 1 Fast Start For Projects  Electric Dipole Moment Project Facilitator:
Effective Project Management: Traditional, Agile, Extreme
Announcement – Career Fair Who: Everyone should plan to go… What: Meet / network with companies Meet hiring managers Get information first hand Where:3.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 4 Project Scope Management.
Refrences: Information Technology Project Management, Sixth Edition(ch#3) Note: See the text itself for full citations.
1 Advanced Project Management Project Plan Templates Ghazala Amin.
Establishing an Agile Testing Team: Our Four Favorite “Mistakes” Kay Johansen Anthony Perkins.
Presented by © Advanced Management Services, Inc Adaptive Project Framework A Common Sense Approach to Managing Complexity and Uncertainty Robert.
Professional Certificate in Electoral Processes Understanding and Demonstrating Assessment Criteria Facilitator: Tony Cash.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
COPYRIGHT TOM SULZER © 2015 IS 455 Oct 1, 2015 Agenda House Cleaning Quick Review Initiate Second Life Project Teams for Second Life Project are the teams.
What is project management?
Project Management.
Prof. Roy Levow Session 2.  Define the Project  Develop a Detailed Plan  Launch the Plan  Monitor / Control Project Progress  Close Out the Project.
Fundamentals of Governance: Parliament and Government Understanding and Demonstrating Assessment Criteria Facilitator: Tony Cash.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Copyright © 2015 John Wiley & Sons, Inc. All rights reserved. Information Technology for Management Chapter 13: Project Management and SDLC Prepared by.
CSSE October.2008 APF: Cycle plan and build Chapters 15 & 16.
Lecture “6” Manage Project Team
INFO 638Lecture #91 Software Project Management Conclude Adaptive Project Framework INFO 638 Glenn Booker.
Adaptive Project Framework
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
IS Project Management Extreme Project Management
Information Technology Project Management – Fifth Edition
Information Technology Project Management – Fifth Edition
Effective Project Management: Traditional, Agile, Extreme
Agile Process: Overview
ETI 4448 Applied Project Management
Effective Project Management: Traditional, Agile, Extreme
IS Project Management Extreme Project Management
FdSc Module 107 Systems Analysis
PROJECT PLANNING AND SCHEDULING BY: AMINATH SHAAYAN SHAHID.
Presentation transcript:

Prof. Roy Levow Session 10

 Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next Cycle Plan

 Explain the significance of each input to the client checkpoint  Assess the status of the completed cycle relative to its plan  Describe the inputs to the next cycle plan  Explain the outputs of the client checkpoint Copyright 2007 John Wiley & Sons, Inc.Chapter 173

 Planned versus Actual Functionality Added  Why wasn’t the planned functionality added in this cycle?  Explain how the functionality will be added in future cycles  Scope Bank  Let customer decide what proposed changes will be added in future cycles Copyright 2007 John Wiley & Sons, Inc.Chapter 164

 What was planned?  What was done?  Is the version scope still valid?  Is the team working as expected?  What was learned? Copyright 2007 John Wiley & Sons, Inc.Chapter 175

 Inputs  Any functionality completed during the previous cycle  Any functionality planned but not completed in the previous cycle  The functionality planned for this cycle  The functionality planned for all the cycles beyond the next one  All learning and discovery that took place in all previous cycles (Scope Bank)  Any items still remaining on the Issues Log  Any changes that took place in the business environment during the previous cycles Copyright 2007 John Wiley & Sons, Inc.Chapter 176

 Outputs  Updated functionality list  Reprioritized functionality list  Next cycle length Copyright 2007 John Wiley & Sons, Inc.Chapter 177

 Checking Explicit Business Outcomes  Reviewing Lessons Learned for Next Version Functionality  Assessing APF for Improvements

 Explain the significance of the Post-Version Review  Describe the deliverables from a Post-Version Review  Conduct a Post-Version Review  Extract lessons learned from the version project Copyright 2007 John Wiley & Sons, Inc.Chapter 189

 To Improve Product  To Improve Process  To Determine if Business Value is Being Delivered Copyright 2007 John Wiley & Sons, Inc.Chapter 1810

 Check Explicit Business Outcomes  The success of the APF project is the business value it delivered  Review Lessons Learned for Next Version Functionality  Assess APF for Improvements Copyright 2007 John Wiley & Sons, Inc.Chapter 1811

 Proof-of-Concept Cycle  Revising the Version Plan  Embedding the APF in Other Approaches  Extreme Project Management  Comparing Project Approaches

 Embed the APF in other approaches  Use the APF for proof of concept  Adapt the APF to revise the version plan  Identify an extreme project  Describe the four phases of the Extreme Project Management approach  Understand how Extreme Project Management clarifies the goal and converges to a solution Copyright 2007 John Wiley & Sons, Inc.Chapter 1913

 Proof-of-Concept Cycle  Used to help make business case for project  First cycle of APF project  Steps  The creation of a prototype  A feasibility study  The writing of use cases  Storyboarding  Any other activity to demonstrate business plan  Revising Version Plan  The first few cycles generates numerous change ideas and issues  Client may decide to change version plan Copyright 2007 John Wiley & Sons, Inc.Chapter 1914

 In TPM  In the WBS, leave a functionality undefined  Place undefined functionality in Network Diagram  Use APF for the undefined functionality Copyright 2007 John Wiley & Sons, Inc.Chapter 1915

 High Speed – Project is innovative, groundbreaking, and vital to organization. Speed is essential  High Change – Uncertainty about goal and solution necessitates constant change  High Uncertainty – Time and cost are unknown Copyright 2007 John Wiley & Sons, Inc.Chapter 1916

 Iterative  After each cycle, decision made to continue or cancel  Scope is unknown  Client most involved (makes decision to go on)  No constrained scope triangle Copyright 2007 John Wiley & Sons, Inc.Chapter 1917

 Define the Project Goal  xPM Project Overview Statement  Establish a Project Timebox and Cost  Establish Number of Cycles and Cycle Length  Trade-Offs in the Scope Triangle Copyright 2007 John Wiley & Sons, Inc.Chapter 1918

 Defining How the Project Will Be Done  Conditions of Satisfaction  Scenarios, Stories, and Use Cases  Prioritizing Requirements  Identifying the First Cycle Deliverables  Go / No-Go Decision  Planning for Later Cycles Copyright 2007 John Wiley & Sons, Inc.Chapter 1919

 How this Phase Differs  Time for exploration and discovery  Subteams share ideas and information  Assign Resources  Establish Cycle Plan  Collaboratively Produce Deliverables Copyright 2007 John Wiley & Sons, Inc.Chapter 1920

 Apply Learning and Discovery from the Previous Cycle  Revise the Project Goal  Reprioritize Requirements  Make the Go / No-Go Decision for the Next Cycle Copyright 2007 John Wiley & Sons, Inc.Chapter 1921

Copyright 2007 John Wiley & Sons, Inc.Chapter 1922