Team Skill 6: Building the Right System Managing Change (28)

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Advertisements

Configuration Management
Dr. Denise Bannan, Mr. Jeff Chapko, Dr. Jill Langen This presentation outlines what steps would have been beneficial, along with deploying some CQIlean.
Prescriptive Process models
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Chapter 3 Project Initiation
Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.
Requirements Structure 2.0 Clark Elliott Instructor With debt to Chris Thomopolous and Ali Merchant Original Authors.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
SE 555 Software Requirements & Specification Requirements Management.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
Chapter 30 Agile Requirements Methods. Mitigating Requirements Risk  The entire requirements discipline within the software lifecycle exists for only.
Course Technology Chapter 3: Project Integration Management.
By Saurabh Sardesai October 2014.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Chapter 4: Project Integration Management
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
Planning. SDLC Planning Analysis Design Implementation.
Change Request Management
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Organizing Requirements & Managing Scope (Chapters of the requirements text ) Steve Chenoweth & Chandan Rupakheti RHIT Which brings up Question 1,
S/W Project Management
Copyright Course Technology 1999
Software Development Life Cycle Decisions Project Management Disciplines Stacey Shearn September 8, 2005.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Project Management Chapter 3. Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing.
1 Chapter 4: Project Integration Management. 2 Learning Objectives Describe an overall framework for project integration management as it relates to the.
Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 6 Integration Management “Bringing it all together”
Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 4 Requirements Specification Integration Management.
Setting Your Fees Project Cost and Setting Your Fees.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
IT Requirements Management Balancing Needs and Expectations.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Requirements and Estimation Process From a CMM Level 5 Organization Alan Prosser.
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Georgia Institute of Technology CS 4320 Fall 2003.
© Mahindra Satyam 2009 Configuration Management QMS Training.
The Long Tail Why the future of business is selling less of more ▫ISBN = ▫Chris Anderson Low Distribution and Inventory costs allow companies.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Introducing Project Management Update December 2011.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
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.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
1 Text Layout Introduction (1-4) Team Skill 1 – Analyzing the problem (5-7) Team Skill 2 – Understanding User and Stakeholder Needs (8-13) Team Skill 3.
Project management Topic 1 Introduction.
System Maintenance Modifications or corrections made to an information system after it has been released to its customers Changing an information system.
T Iteration Demo Team DTT Project planning (PP) Iteration
Degree and Graduation Seminar Integration Management
4.5 Perform Integrated Change Control
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.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
1 Software Maintenance and Evolution CSSE 575: Session 4, Part 2 Software Maintenance Process Steve Chenoweth Office Phone: (812) Cell: (937)
Team Skill 2 Understanding User and Stakeholder Needs The features of a Product or System (9)
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
1 Introduction Overview This annotated PowerPoint is designed to help communicate about your instructional priorities. Note: The facts and data here are.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Project Management Finals Lesson 1 - Principles - Techniques - Tools.
1 Chapter 4: Project Integration Management. 2 Learning Objectives Describe an overall framework for project integration management as it relates to the.
Change Request Management
Software Project Configuration Management
Managing the Project Lifecycle
Chapter 3 – Agile Software Development
Extreme Programming.
Chapter 4: Project Integration Management
Chapter 3: Project Integration Management
Project Kick-off <Customer Name> <Project Name>
Presentation transcript:

Team Skill 6: Building the Right System Managing Change (28)

Managing Change Key Points ▫Managing requirements must account for change to be successful ▫Internal/External factors play an important role ▫The process must be followed in order to achieve success 2

Managing Change What external factors effect requirements ▫The problems the system is going to address has changed ▫Competition from others in the same market place ▫Stakeholders needs and wants change  Or New stakeholders ▫New regulatory or legal changes 3

Managing Change Figure 28-5 Overview 4

Managing Change Additional external factors ▫Changes in environment  Hardware changes  Software changes  Technology changes  Green screens  Windows  Websites  Web services  … ▫Feedback from current users  Customer Steering Committees  Customer Advocates 5

Managing Change External Factors ▫Are usually beyond the control of your team  Some are a direct result the teams activities  Others as we have seen come from sources beyond our control 6

Managing Change What are the internal factors? ▫This is something we have more control over.  Must perform our due diligence ▫Trying to uncover as many requirements as possible  Involve stakeholders, SMEs from every area  Formulate lists of questions ▫Processes  Documentation standards  Requirements change process ▫Poorly defined Requirements/Processes can lead to interpretation /misinterpretation 7

Managing Change Strengths of the Iterative Process ▫Reveal change  Each iteration gives stakeholder visibility into the project  Receive feedback ▫Requirements are not frozen ▫Handle change to existing requirements through refactoring ▫Change priority after each iteration ▫New requirements can be added after each iteration  Allows us to engage the customer 8

Managing Change About 50% of new requirements originated from unofficial sources (Weinberg) Customer expectations ▫2x-5x than the amount of available resources ▫At the start of a project Managing Requirements starts from the beginning 9

Managing Change How do we make a change management strategy ▫Components  Plan for change  Baseline after each iteration  Refer to the chapter on baselines  Have a single resource for control  Have a system to control the process 10

Managing Change Plan for change ▫All requirements submitted are considered valid  That’s why we have  Prioritization  Pruning  … ▫Requirements coming from technical members should reviewed with stakeholders Baseline after each iteration ▫Make sure to baseline after each iteration! ▫Baselines are done after a client verified iteration ▫Maintain a list of prioritized use cases 11

Managing Change Have a single source of control ▫Eliminate changes coming from every direction ▫Avoid being nickel and dimed  Must be accountable the impact of a change ▫This can be:  Change control board (CCB)  Triage Meetings  … ▫Keep CCB as small  Key member from each team  Business  Development  QA  All must have strong negotiation skills and estimation skills 12

Managing Change Have a change control system ▫Enter requested change  Be specific and clear in your description ▫Set the impact/risk level ▫Time Estimate  Man hours ▫Set the priority  How important is the change CCB ▫Here you can set these values ▫Schedule the changes ( now | later | defer | reject ) A member from each team is present so everyone has input and is aware of the change 13

Managing Change Figure 28-1 Capturing Changes 14

Managing Change Figure 28-2 Change Request Flow 15

Managing Change Figure 28-3 Ripple Effect of changes 16

Managing Change Configuration management ▫Supports change management process ▫Prevents unauthorized changes and allows rollbacks ▫Prevents accidents  Overwriting  Conflicting revisions ▫Automated tool required 17

Managing Change What are the 3 levels of change management ▫Finest level  The lowest level  Individual use cases/requirements ▫Medium level  Large enough to need  Revision history of the changes ▫When/what changes ▫Provides the ability to rollback to different versions ▫Highest level  Records of changes for the entire project 18

Managing Change Personal Experience ▫Team skills are very important to effective change management  Communication  Technical  Estimation Experience ▫Handling change includes  What will be delivered  What the customers expect  How this impacts the business ▫When handling changes the PM must be responsible for negotiating what gets done ▫Designs are constantly up for negotiations until they are baselined  Then they still are not completely safe 19

Managing Change What I always do ▫Document everything  Design decisions both why and why not  Meeting notes  s ...  Validates your decisions (VOB)  Supports due diligence ▫Rely on techniques learned throughout this class  Interviews (CSC)  Elicitation Meetings  … 20