Class 6 – Scope Management Group Project 2 Project strategy – how to attack it Inception skills requirements Planning technique requirements Scope Management Scope creep & time boxes: major advantages of phases Strategies for planning phases to manage scope Team management, clear responsibilities, simultaneous tasks Client Project Bidding – Friday noon Group Project 2 meeting 1

Group Project 2 : Requirements Inception – 1st iteration Analysis – Design – Construction - Review Delivery 1. One-page executive summary Delivery 2. Strategy discussion summarizing the relevance of the details in deliveries 3 – 9 Delivery 3. Organizational Impact Statement Delivery 4. Functional Requirements Priorities Table Delivery 5. Non-Functional Requirements Summary Delivery 6. Risk Evaluation and Risk Reduction Strategies

Group Project 2 : Requirements Inception – early planning Delivery 7. Milestone summary (summary of phases) Delivery 8. Network diagram (overview graphic of phases) Delivery 9. Gantt chart -- for development team (MS Project)

GP 2 – Resources 4

GP 2 – Planning Resources 5

How does Group Project 2 compare with the client project ? 6

Class 6 – Scope Management Group Project 2 Project strategy – how to attack it Inception skills requirements Planning technique requirements Scope Management Scope creep & time boxes: major advantages of phases Strategies for planning phases to manage scope Team management, clear responsibilities, simultaneous tasks Client Project Bidding – Friday noon Group Project 2 meeting 7

Scope Management

Managing Scope Creep With Time Boxes Finish: 10/27 FBLA example, p. 3 in Day 5 reading: “Planning IT Projects”

Strategies for Planning Phases Choose phases that are meaningful to users so reviews are effective. Order your phases based on project priorities: What is urgent? What could be a quick value added? What is key to understanding requirements? What is key to determining broad based design issues? What is key to the rest of development? (reading posted for today’s class) 10

Gantt Chart View of MS Project 11

Proposed Library Control System: Major Milestone Summary Phases and Milestones Week Ending Date Phase 1: Preliminary Investigation Weeks 1-4 March 23 Phase 2: Design System Database Week 5 March 30 Phase 3: Administration Module Week 6 April 10 Phase 4: Resource Tracking /Search Module Week 6 April 10 Phase 5: Check-in/Check-out Module Week 7 April 18 Phase 6: Report Generation Module Week 7 April 18 Phase 7: On-line Help Module Week 8 April 27 Phase 8: Additional Functionality Module Week 8 April 27 Phase 9: Installation and System Testing Week 9 May 8 Phase 10: Documentation and Training Week 10 May 15 12

Gantt Chart View of MS Project Team management, clear responsibilities, simultaneous tasks --- all on the Gantt Chart @ detail level & Overview 13

Data includes the Phase Label, Task #, Length, Start & Finish, & “Resource” Names You can switch between the Gantt Chart view and Network Diagram views in MS Project. This is a Network Diagram with the details collapsed so only the Phases are shown. 14

Week 7 Week 6 Week 6 Week 6 Week 8 The Network Diagram view shows simultaneous work more clearly than the Gantt chart view. 15

Managing Scope Creep With Time Boxes Missing this time box led to a redefined schedule and focus.

At each User Review Point, check for changes in Scope, Schedule and Resources Scope Has the scope changed? Did we hit our schedule target date?   Schedule Resources Have we lost team members that impact the schedule? Do we need team members with different skills?

EMS Scheduling Project This was a project to automate scheduling of drivers and medical staff for the City of Austin’s Emergency Medical Services.

Project Objectives Automate scheduling Alert managers to scheduling conflicts Staffing reports Create an electronic scheduling form

Preliminary DFD Daily Schedule Payroll Procedure Monthly Schedule Overtime Daily Schedule Trades Payroll Procedure Leave Reports

No problem! We can do that. And now the rest of the story….

Daily Schedule Payroll Procedure OJI Monthly Schedule Payroll Overtime Training Monthly Schedule Mandatory OT list Reassignments Leave Data Vacation Payroll Continuing Education Overtime Workload Rule Daily Schedule Payroll Procedure Trades Leave The team worked out a new scope with the client so they did initial requirements definition and recommended completing development over the next two semesters by new 374 teams. Leave Accrual Holdovers City Certification Reports State Certification Callbacks Sick Time Leave Cap Unfilled Positions Overtime Per Shift OJI

Scope Revised: Overview of Automated Resource Management System (ARMS) Once the spring 1998 MIS 374 team determined that creating an automated payroll system was too complex for one semester they took several actions. They renamed the project an Automated Resource Management System (ARMS) and split the work into 4 major phases that would be done by 4 teams over 3 semesters. This slides shows the overview of what must be completed as well as the focus of the initial spring 1998 team. The next slide shows the work to be done by all 4 teams.

Overview of 3-semester plan for ARMS This slide shows the work to be completed by 4 teams over 3 semesters: Spring 1998 – the original EMS team would complete a requirements specification and design for an internal system to be used by the main office. Fall 1998 team 1 – implement the internal system to be used by the main office using the analysis and design specifications provided by the spring 1998 team Fall 1998 team 2 – complete a requirements specification and design for the distributed portion of ARMS to allow the Mobile Medic Units, Medic Stations, and Banner System to interact with the internal system Spring 1999 – implement the distributed portion of the system based on the analysis and design specifications provided by the fall 1998 team 2.

Hey, I have an idea! Wouldn’t it be nice if… CHALLENGE: SCOPE CREEP Hey, I have an idea! Wouldn’t it be nice if… BACKGROUND CHALLENGES SOLUTIONS LESSONS 25

SCOPE CREEP CHALLENGE: Yuli – Great coder, could code anything “Some team members feel that we can code functionality easily without thinking about testing. There are a lot of complications you have to take into account for every additional requirement.” -Ameer “I think there should have been a better balance regarding how much we can/should sign up for. Some team members were too quick to sign up for new things, while others were too slow.” -Guillermo -Scope creep requirements (reports to modify/add new session times, semi-scheduling piece, when we agreed we would not do scheduling already) Yuli – Great coder, could code anything Ameer – Tester and wouldn’t implement a piece of coder Karen – Was the PM BACKGROUND CHALLENGES SOLUTIONS LESSONS 26

SCOPE CREEP + SOLUTION: Evaluation Table Gantt Chart Also, “tabling” items To this day we still have minor disagreements about how much we can take on. BACKGROUND CHALLENGES SOLUTIONS LESSONS 27

SOLUTION: SCOPE CREEP -Karen kept us focused on what we promised and discouraged adding extras as we went along. Hitting our deadlines for already promised functions was critical. Eleanor and Sharon’s added note: Karen called herself “the main manager of the Gantt chart,” rather than the Gantt Chart queen, like the team member in the ASTA case in the text. BACKGROUND CHALLENGES SOLUTIONS LESSONS 28

Class 6 – Scope Management Group Project 2 Project strategy – how to attack it Inception skills requirements Planning technique requirements Scope Management Scope creep & time boxes: major advantages of phases Strategies for planning phases to manage scope Team management, clear responsibilities, simultaneous tasks Client Project Bidding – Friday noon Group Project 2 meeting 29

4 Group Project Grades: Average is 20% of final grade GP 1 grade 1 - analysis GP 1 grade 2 - diagrams GP 2 grade 1 - analysis GP 2 grade 2 - planning Move all the GP grade slides to 24th

Group Project 1 4 grades explained appeal process will avg usually 88 to 97 Grade 2 (diagrams): avg usually 85 to 95 4 grades explained appeal process will be posted next week 31

Group Project 1 rubrics on Clint’s door 32

Group Project 2 – Meeting now 33