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