Envisionment Phase Schedule

Go back to the Gantt view and enter the information below into the schedule. The numbers in parentheses represents how far you should indent the item. Each time the indentation changes, we will list it in the first column in parentheses. A 0 means the item is all the way to the left, a 1 means it is indented once, etc. Make sure that all constraints are set as soon as possible.

Name

Start Date

Duration

Resources

Predecessors

1 (0)

Notes about this template

Mon 01/17/00

0 days

When you are entering the following information, please bear in mind that the durations I have given to the goals here are only estimates, based on showing you what a realistic schedule may look like. In real life, the durations will vary according to the size and complexity of the project, the number of people available, what else team members may be working on at the same time, and lots of other factors. This schedule merely serves as an example for the project we have been looking at throughout the book.

Name

Start Date

Duration

Resources

Predecessors

2

Envisionment

Mon 01/17/00

3 (1)

Evaluate current systems / meet with client mgmt

Mon 01/17/00

Management, Product Management, Component Manager 1, Component Manager 2, Component Manager 3

Architecture

Document

Fri 01/21/00

0 days

3

Name

Start Date

Duration

Resources Predecessors

5

Initial

Mon 01/24/00

1 day

Component Manager 1, 4

Consensus

Developer 1a, Tester

Meeting

1a, Developer 1b,

Tester 1b, Component

Manager 2, Developer

2a, Tester 2a,

Developer 2b, Tester

2b, Component

Manager 3, Developer

3a, Developer 3b,

Tester, Product

Management, Project

Manager, Educator,

Logistics, End

Users, Client

Management

In the first part of the envisionment phase, we must evaluate how the client's current Enterprise system works and what their current business processes are. This is essential to give us a good idea of the background of the client. We must then determine how that system will be integrated, or migrated, into the current project.

It is important that every team member attends the initial consensus meeting: everybody should understand the aims of the project and the impact it will have on the client.

It is quite obvious that the Enterprise Architecture Document cannot be created until you have evaluated the current system. Similarly, the initial consensus meeting cannot take place until the current status of the business is known and can be communicated to all.

Name

Start Date

Duration

Resources

Predecessors

6

Define Vision / Scope

7 (2)

Determine ROI and TCO

Tue 01/25/00

6 days

Logistics[50%)

5

8

Initial ROI and TCO estimates

Tue 02/01/00

0 days

7

This part of the envisionment phase allows you to make an initial estimate of the Total Cost of Ownership and Return On Investment for the project. At this stage, estimates will be just that - it is only after completing the other phases of the project that these estimates can be refined.

The ROI and TCO cannot be determined until after the initial consensus meeting. Similarly, the milestone cannot be reached until the ROI and TCO have been determined.

Name

Start Date

Duration

Resources

Predecessors

9

Define Client Requirements

Tue 01/25/00

4 days

Educator

5

10

Define content requirements

Tue 01/25/00

2 days

Component Manager 3

5

11

Define system requirements

Tue 01/25/00

6 days

Logistics[50%]

5

12

Define client / server requirements

Tue 01/25/00

2 days

Component Manager 1, Developer 1a, Developer 1b

5

13

Define specific functionality

Tue 01/25/00

1 day

Component Manager 2, Developer 2a, Developer 2b

5

As you are undertaking the project to deliver some specific functionality to the user, it would be very useful to find out what it is that they require! This cannot take place until after the initial consensus meeting. To define client requirements, you must decide not only what information the users require, but also how they prefer to access that information. From this, you should be able to determine exactly what information each user requires.

Your clients may have strict rules about the configuration of their computers. This may put restrictions on the way that the project can be designed and developed. It is imperative that information such as this is uncovered before any design or development takes place - knowing the restrictions beforehand will save a lot of money and effort in the long run.

To define the specific functionality, you must take the user requirements and translate them into goals for the developers; this will give them more of an idea of what it is they are expected to do when design and development actually take place.

Name

Start Date

Duration

Resources

Predecessors

14 Define risks and Wed risk management 02/02/00

approach

4 days

Component Manager 1, Developer 1a, Tester 1a, Developer 1b, Tester 1b, Component Manager 2, Developer 2a, Tester 2a, Developer 2b, Tester 2b, Component Manager 3, Developer 3a, Developer 3b, Tester, Product Management, Project Manager, Educator, Logistics, End Users, Client

Management

It is important to analyze your concept, the environment you are working in and the potential problems that could arise. These areas of risk should be documented and a plan formulated to mitigate the risk where possible, and manage the risk where necessary. Depending on the degree of risk inherent in the project, you may want to add contingencies to the durations in the project plan. This step would form the basis of the Risk Assessment Document.

This step cannot take place until all the preceding steps have been completed: the risks identified will be specific to what the user wants the system to do. Until the specific functionality and requirements have been defined, the risks cannot be identified.

Name

Start Date

Duration

Resources

Predecessors

15

Develop project plan

Tue 02/08/00

2 days

Component Manager 1, Developer 1a, Tester 1a, Developer 1b, Tester 1b, Component Manager 2, Developer 2a, Tester 2a, Developer 2b, Tester 2b, Component Manager 3, Developer 3a, Developer 3b, Tester, Product Management, Project Manager, Educator, Logistics, End Users, Client Management

14

16

Develop Testing Plan for project

Thu 02/10/00

4 days

Tester 1a, Tester 1b, Tester 2a, Tester 2b, Tester

15

17

Create Master Schedules

Thu 02/10/00

1 day

Component Manager 1, Component Manager 2, Component Manager 3

15

The project plan should answer the following questions:

> What is the business problem being addressed by this project?

> Who are the users and what are their specific goals?

> Who are the stakeholders and sponsors and what are their specific goals?

> What will the client gain as a result of this project?

It should also take account of potential risks, so this step cannot take place until the risks and risk approach have been defined.

A testing plan should also be developed to ensure that all code is tested systematically and thoroughly. The master schedule should also be created; this gives an idea as to how long the project will last and can also provide initial cost estimates for the project. These two steps will follow on from the project plan.

Name

Start Date

Duration

Resources

Predecessors

Final

Consensus Meeting

Wed 02/16/00

1 day

Component Manager 1, Developer 1a, Tester 1a, Developer 1b, Tester 1b, Component Manager 2, Developer 2a, Tester 2a, Developer 2b, Tester 2b, Component Manager 3, Developer 3a, Developer 3b, Tester, Product Management, Project Manager, Educator, Logistics, End Users, Client Management

16,17,15

Vision / Scope Document Complete

Wed 02/16/00

0 days

The final consensus meeting, again attended by every team member, will give the green light for the project. All items should have been agreed upon, and the Vision / Scope document created, becoming the milestone for this phase. The completed Vision / Scope document will be used as a tool to communicate with the development team, whether they are an internal development team or an external vendor. As a result of the briefing you should have committed development resources for the project. Quite obviously, this step cannot take place until all preceding steps are complete.

The Vision / Scope document should include:

> Vision statement

> Scope statement

> Assessment of resources

> Team responsibilities

> Risk Assessment

The schedule for the Envisionment phase will look as follows in Project

The schedule for the Envisionment phase will look as follows in Project

To make the schedule more readable, you can change the color of the goals that are divided into smaller goals. Select an entire row and then go to Format | Font and select a color.

The Gantt chart will look as follows:

Was this article helpful?

0 0
365 Days Of Motivation

365 Days Of Motivation

Stop Wasting Time And Learn How To Stay Motivated. Finally! Discover How To Stop Your Mind From Wandering, And Upgrade Your Motivation. You Can Hack Your Motivation Levels, Allowing You To Take Your Life To The Next Level.

Get My Free Ebook


Post a comment