class 6 – scope management group project 2 1.project strategy – how to attack it 2.inception...

Class 6 – Scope Management Group Project 2

1. Project strategy – how to attack it2. Inception skills requirements3. Planning technique requirements

Scope Management 1. Scope creep & time boxes: major

advantages of phases2. Strategies for planning phases to manage

scope 3. Team management, clear responsibilities,

simultaneous tasks

Client Project Bidding – Friday noon

Group Project 2 meeting

Group Project 2 : Requirements Delivery 1. One-page executive summaryDelivery 2. Strategy discussion summarizing the relevance of the details in deliveries 3 – 9Delivery 3. Organizational Impact StatementDelivery 4. Functional Requirements Priorities TableDelivery 5. Non-Functional Requirements SummaryDelivery 6. Risk Evaluation and Risk Reduction Strategies

Inception – 1st iteration Analysis – Design – Construction -

Review

Group Project 2 : Requirements

Delivery 7. Milestone summary (summary of phases)Delivery 8. Network diagram (overview graphic of phases)Delivery 9. Gantt chart -- for development team (MS Project)

Inception – early planning

GP 2 – Resources

GP 2 – Planning Resources

How does Group Project 2 compare with the client project ?






simultaneous tasks



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:1. What is urgent?

2. What could be a quick value added?

3. What is key to understanding requirements?

4. What is key to determining broad based design issues?

5. What is key to the rest of development? (reading posted for today’s class)

Gantt Chart View of MS Project

Proposed Library Control System:Major Milestone Summary

Phases and Milestones Week Ending Date

Phase 1: Preliminary Investigation Weeks 1-4 March 23Phase 2: Design System Database Week 5 March 30

Phase 3: Administration Module Week 6 April 10Phase 4: Resource Tracking /Search Module Week 6 April 10

Phase 5: Check-in/Check-out Module Week 7 April 18Phase 6: Report Generation Module Week 7 April 18

Phase 7: On-line Help Module Week 8 April 27Phase 8: Additional Functionality Module Week 8 April 27

Phase 9: Installation and System Testing Week 9 May 8Phase 10: Documentation and Training Week 10 May 15

Gantt Chart View of MS Project

Team management, clear responsibilities, simultaneous tasks --- all on the Gantt Chart @ detail level & Overview

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.

Data includes the Phase Label,

Task #,Length,

Start & Finish,& “Resource”

Names

The Network Diagram view shows simultaneous work more clearly than the Gantt chart view.

Week 6 Week 8Week 7Week 6Week 6

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 ResourcesScope

Schedule

Resources

Have we lost team members that impact the schedule?

Do we need team members with different skills?

Has the scope changed?

Did we hit our schedule target date?

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

MonthlySchedule

Overtime

Trades

Leave

Reports

Payroll

Procedure

Daily Schedule

Preliminary DFD

No problem!

We can do that.

And now the rest of the story….

Trades

Leave

Reports

Leave Data Reassignments

Callbacks

City Certification

State Certification

Continuing Education

Mandatory OT list

Holdovers

SickTime

Payroll

Vacation

Unfilled Positions

LeaveAccrual

Overtime Per Shift

Training

WorkloadRule

OJI

Leave Cap

Monthly Schedule

Overtime

Payroll

ProcedureDaily

Schedule

Scope Revised: Overview of Automated Resource Management System (ARMS)

Overview of 3-semester plan for ARMS

SCOPE CREEP

BACKGROUND CHALLENGES SOLUTIONS LESSONS

CHALLENGE:

Hey, I have an idea! Wouldn’t it be nice

if…

SCOPE CREEP


CHALLENGE:

“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


SOLUTION:

Alternative 1: Preliminary investigation and analysis only

Alternative 2: Registration System

Alternative 3: Registration + Conference Management System

Alternative 4: Registration + Conference Management + Scheduling System

Key Features -Complete investigation, documentation, and analysis -Prototypes of system

-Same as alternative 1 -Automates most registration processes -VB.net and SQL backend

-Same as alternative 2 -Automates most conference level processes

-Same as alternative 3 -Automates scheduling processes

Advantages -Users will have better understanding of proposed system with prototypes -Users can give constant feedback which will be used to improve prototypes -Will show how system will be integrated -DFD diagrams clarify data flows of old and new system -Comparison of components for old and new system -Easier for teams to start developing system next semester

-Can be completed by team, given time constraints -Avoids duplicate data input -Scalable to support future system growth (to incorporate conference management and scheduling system) -Reports will make scheduling process easier -Online

-Single database handles all FBLA processes -Supports future growth (Scheduling system) -Online

-Single database handles all FBLA processes -Fully functioning system -Online

Disadvantages -No functioning back end -No functioning front end -Even if teams begin developing next semester, functioning parts of the system will not be ready by February 2009

-Not fully complete -Two separate databases are still needed in order to handle conference management processes

-Cannot be completed this semester -Does not automate scheduling process --Lack of continuity of development (Learning curve for future teams)

-Cannot be completed this semester -Lack of continuity of development (Learning curve for future teams) -Phases may be cut short due to time constraints, which means end result could be a system with no component being fully functional

Questions -What types of prototypes are needed? -What functions need to be demonstrated to users before construction?

-What information is needed in reports? -Can team work with SQL server and VB.Net?

-Can FBLA work with another team next semester to finish work?

-Can FBLA work with another team next semester to finish work? -Can FBLA hire professional programmers for scheduling system?

Evaluation Table

Gantt Chart

+

SCOPE CREEP


SOLUTION:






simultaneous tasks



4 Group Project Grades:Average is 20% of final grade

GP 1 grade 1 - analysisGP 1 grade 2 - diagrams

GP 2 grade 1 - analysisGP 2 grade 2 - planning

Group Project 1

Grade 1: 88 to 97

Grade 2 (diagrams): 85 to 95

4 grades explained

appeal process

Group Project 1

Group Project 2 – Meeting now

class 6 – scope management group project 2 1.project strategy – how to attack it 2.inception...

Documents

scope management slide

meeting slide

guillermo slide

scope management group

project strategy

project priorities

level overview slide

project objectives