pm - ganaxa case study & assignment - a project...

Project Management

Ganaxa case study & assignment:

a project plan

[email protected]

Project: creating the Ganaxa website (1)

Project: creating the Ganaxa website (2)

Assumptions: Work to do

YOU (the PM) must now establish a PROJECT PLAN to be

given to the CO (on May 16, 2017 at the latest...).

The plan must cover everything to be done in order to

complete the project following the agreement on the

requirements (already obtained, as stated on the previous

page...), ie from content creation and site design to project

closure, not forgetting overall project management.

The plan must clearly show the project's tasks, task

sequencing, resources and resource allocation, schedule and

cost.

Assumptions: WBS Content creation Site development Project management

Write bios

Translate bios

Procure other pictures

Produce diagram

Design site

Code site

Integrate content

Test site, fix bugs, re-test

Deploy site & go live

Manage/Supervise project

Accept site

Install & configure Wiki Review, adjust & agree on design

Close project

Call for content

Write other texts

Translate other texts

Assumptions: Resources *

Thibault de la Rivière

TC

TJ

CO

Staff

External contractor

PM (YOU!)

PM

TC

TJ

OC

DD

CO

€

OC group member

OC group member

OC group member

OC group member

Graphic Designer & Web Developer

Company Owner / Project Sponsor

Project Manager (& major contributor)

Translator/Tester – Chinese (& English)

Translator/Tester – Japanese (& French)

Other (minor) Contributors (group of 4)

* No more, no less!

Assumptions: Costs *

Thibault de la Rivière

TC

TJ

CO

Staff

External contractor

PM (YOU!)

PM

TC

TJ

OC

DD

CO

€

OC group member

OC group member

Not taken into account

€ 500 per day

€ 320 per day

€ 300 per day

Not taken into account

€ 650 per day * No costs other than labour!

OC group member

OC group member

Assumptions: Resource assignment Approves* site design; writes his own bio & other texts (in FR); procures pictures; accepts website; participates in closure.

Manages the project part-time [25%]; issues "call for content"; installs wiki; approves* site design; writes his own bio (EN & FR); translates texts (FR <-> EN); draws GPP diagram (EN & FR); participates in testing; accepts website; participates in closure.

Writes her own bio (CH & EN); translates texts (EN -> CH); participates in testing part-time [25%]; participates in closure.

Writes her own bio (JA & FR); translates texts (FR -> JA); participates in testing part-time [25%]; participates in closure.

Write their own bios (in FR). Thibault de la Rivière

TC

TJ

CO

Staff

External contractor

* "approves" is short for "reviews, adjusts and agrees on"

PM (YOU!)

PM

TC

TJ

OC

DD

CO

€

OC group member

OC group member

Designs the site, enhances GPP diagram & approves* site design; codes the site; integrates content; fixes technical bugs; deploys the site; participates in closure.

OC group member

OC group member

Assumptions: Content 17 pages of text in total to write and/or translate:

8 biographies ("bios") (written in FR by each person concerned, translated by PM, TC & TJ)

8 other pages of text (written in FR by CO, translated by PM, TC & TJ)

1 page of text in GPP diagram (written in FR & EN by PM, translated by TC & TJ)

Pictures:

GPP diagram (prepared by PM, translated by TC & TJ, then enhanced by DD for the site)

Other pictures (procured by CO)

Editorial specifications are included in the Requirements

Specification ("editorial design" task not required in the plan).

Assumptions: Task workloads/durations *

Writing 5 of the 8 bios (the CO's + the OC's)

Procuring other pictures

Writing or translating 1 page of text

Drawing (with text in EN & FR) then enhancing

the GPP diagram (after translation into CH & JA,

and after site design)

5 person-hours spread over 3 days

1 person-day spread over 4 days

4 person-hours

1 person-hour (on average)

(* Including proofreading when relevant, formatting and uploading to the wiki)

4 person-hours

(drawing, with text, by PM) (enhancing, by DD)

Project management 25% of PM's time from day 2 through to deployment

Other assumptions (1) The PM launches the editorial part of the project by issuing a

"call for content" (ie an e-mail to all contributors) on day 1.

Editorial contributors other than the PM start work on day 2.

A wiki is installed & configured (by the PM) on day 1 and used

for delivery of content to the DD (upload/download).

Final content (fully proofread, therefore bug-free, and properly

formatted) is uploaded to the wiki as it is produced by editorial

contributors, then, after the site has been coded, is downloaded

by the DD and integrated into the site ("container").

(Sample content was already given to DD at the preliminary meeting, so there

is no need to include "Sample content preparation/delivery" in the plan.)

Other assumptions (2) CO has committed to writing the "other 8 pages of text" (in

French) on day 2.

CO has committed to "procuring pictures" (other than the GPP

diagram) but cannot work on the task full time, which is why the

assumed 8-person-hours workload is spread over 4 days (starting

whenever possible...).

CO & OC (the group of 4 "Other (minor) Contributors") are not

readily available for "writing their own bios" (in French), which is

why the assumed 5-person-hours workload is spread over 3 days

(starting on day 2).

TC & TJ are available as of day 2.

PM and DD are available as of day 1.

Constraints Start date = May 29, 2017

Total duration of project no longer than 3.5 weeks

(Finish date no later than June 21, 2017)

8 hours per working day (standard setting in MS Project)

5-day weeks (no work on weekends)

Public holidays not taken into account (to keep things simple!)

Nobody to work more than 100% of her/his time, except for

the PM and the CO, who may work up to 130% of their time

Total labour cost of project no greater than € 18,000

Imagine YOU are the PM for this project!

Take into account the relevant information given on the

previous pages of this document.

Download, copy & complete the project plan (.mpp/.pod):

1) define resources (with unit costs) in the "Resource

sheet" (use the given 2-letter abbreviations to name resources!);

2) enter appropriate "Resource Names" information in

the "Gantt chart";

3) enter appropriate "Predecessors" information in the

"Gantt chart", featuring parallelism between tasks

whenever possible.

using MS Project or ProjectLibre

Assignment instructions (1)

Note: you may need to adjust durations at the lowest level of the WP/task hierarchy to their initial values (as they appear in the incomplete plan provided).

PM

Project GANAXA – Plan to complete (.mpp)

Will be (re)calculated automatically

? ?

Durations at the lowest level should have the same values in the completed plan as they have here.

Project GANAXA – Plan to complete (.pod)

Will be (re)calculated automatically

? ?

Durations at the lowest level should have the same values in the completed plan as they have here.

Check & double-check your project plan!!

Send your plan (a single ".mpp" or ".pod" file) to [email protected]

as soon as possible before Wednesday May 17, 2017.

Failure to meet the deadline will result in a 0 (zero) grade!

Name your file as follows: "YOURNAME_GX_PLAN...", where...

"YOURNAME" is your "FAMILY NAME" (eg "SINGH_GX_PLAN.mpp")

Failure to comply with this file naming convention will result in a penalty!

Assignment instructions (2)

(Failure to comply with the resource naming convention ( 2-letter abbr.) will also result in a penalty!)

mailto:[email protected]

Reminder: Project phases (1)

Business case

Advisability study

Feasibility study

Execution Closure Planning

Plan implementation

Product creation

Project supervision

Requirements

Charter

Scope

Schedule

Budget

Product launch

Project plan

Summary requirements

Reminder: Project phases (2)

Business case

Advisability study

Feasibility study


Plan implementation

Product creation

Project supervision

Requirements

Charter

Scope

Schedule

Budget

Product launch

Project plan

Requirements Integration Design Testing &

Acceptance Deployment

Content creation

Software coding


Execution

Project phases relevant to assignment

Business case

Advisability study

Feasibility study

Closure Planning

Plan implementation

Product creation

Project supervision

Requirements

Product launch

Project plan

Requirements Integration

Design

Testing & Acceptance

Deployment

Content creation

Software coding

Charter

Scope

Schedule

Budget

Provided by the Company Owner

Done by the Project Manager


Produced in preliminary meeting/workshop

Project plan

Project phases to be covered by the plan

Business case

Advisability study

Feasibility study


Plan implementation

Product creation

Project supervision

Requirements

Charter

Scope

Schedule

Budget

Product launch

Requirements Integration Testing &

Acceptance Deployment

Content creation

Software coding

Design

Reminder: Project planning processes

Define scope & collect

requirements

Develop schedule Determine budget

Create WBS

Define tasks

Sequence tasks

Estimate task resources

Plan procurements

Estimate costs

Plan communications

Plan quality

Estimate task durations

Develop human resource plan

Plan risk management,

identify & analyze risks

Processes relevant to assignment

Define scope & collect

requirements

Develop schedule

Create WBS

Define tasks

Sequence tasks


Plan procurements

Plan communications

Plan quality


Develop human resource plan

Plan risk management,

identify & analyze risks

Determine budget Estimate costs

Reminder: Interdependent processes

Sequence tasks



Develop schedule

Questions?

A project plan

Assumptions: WBS Content creation Site development Project management

Write bios

Translate bios


Produce diagram

Design site

Code site

Integrate content

Test site, fix bugs, re-test

Deploy site & go live

Manage/Supervise project

Accept site

Install & configure Wiki Review, adjust & agree on design

Close project

Call for content

Write other texts


Content creation diagram (1) Create Wiki

Call for content

PM PM

done on day 1

Content creation diagram (2)

Write own bio in English & French

Draw diagram

Create Wiki

Call for content

CO

PM

Write 5 bios in French

Write other 8 pages of text in French

PM PM

PM

CO

Write own bio in Japanese & French

Write own bio in Chinese & English

TJ

TC

OC

started on day 2, spread over 3 days

done on day 2

done on day 2



Draw diagram

Create Wiki

Call for content

CO

PM



PM PM

PM

CO

Translate diagram text into Japanese

Translate diagram text into Chinese

TJ

TC



TJ

TC

OC

done on day 2


done on day 2

done on day 2



Draw diagram

Create Wiki

Call for content

PM

CO

PM



Translate 8 pages into English

Translate 8 pages into Japanese

PM PM

PM

TJ

CO



TJ

TC



TJ

TC

CO


OC

done on day 3





Draw diagram

Create Wiki

Call for content

PM

CO

PM




Translate 8 pages into Chinese


PM PM

PM

TC

TJ

CO



TJ

TC



TJ

TC

CO


OC

done on day 4

completed on day 4




Translate 7 bios into English (or French)

Draw diagram

Create Wiki

Call for content

PM

CO

PM






PM PM

PM

PM

TC

TJ

CO



TJ

TC



TJ

TC

CO


OC

done on day 5





Draw diagram

Create Wiki

Call for content

PM

CO

PM



Translate 7 bios into Chinese




PM PM

PM

PM TC

TC

TJ

CO

Translate 7 bios into Japanese

TJ



TJ

TC



TJ

TC

CO


OC

done on day 6

completed on day 6




Draw diagram

Create Wiki

Call for content

PM

CO

PM



Translate 7 bios into Chinese




PM PM

PM

PM TC

TC

TJ

Enhance diagram

DD

CO

Translate 7 bios into Japanese

TJ



TJ

TC



TJ

TC

CO


OC

Project network diagram (1) Create Wiki

Call for content

Design site

PM

DD

PM

done on day 1

started on day 1

Project network diagram (2)

Write other texts

Draw diagram

Create Wiki

Translate diagram

Call for content

Overall project management

Design site

Write bios

PM

CO

PM [25%]

DD

TC, TJ, OC

PM PM TC, TJ

CO

PM

started on day 2, spread over 3 days for CO & OC

done on day 2

continued on day 2

done on day 2 as of day 2


Write other texts


Draw diagram

Create Wiki

Translate diagram

Call for content


Design site

Write bios

Translate bios

PM

CO

PM [25%]

DD

TC, TJ, OC

PM, TC, TJ

PM PM TC, TJ

PM, TC, TJ

CO

PM


CO

done on day 3 and day 4

done on day 5 and day 6

continued on day 3



Write other texts


Draw diagram

Enhance diagram

Create Wiki

Translate diagram

Call for content


Design site

Write bios

Translate bios

PM

CO

PM [25%]

DD

TC, TJ, OC

PM, TC, TJ

PM PM

DD

TC, TJ

PM, TC, TJ

CO

PM


CO

completed on day 3


Write other texts


Draw diagram

Enhance diagram

Create Wiki

Translate diagram

Review, adjust & agree on design

Call for content


Design site

Write bios

Translate bios

PM

CO

PM [25%]

DD

TC, TJ, OC

PM, TC, TJ

PM PM

DD

TC, TJ

PM, DD, CO

PM, TC, TJ

CO

PM


CO

done on day 4


Write other texts


Draw diagram

Enhance diagram

Code site

Create Wiki

Translate diagram


Call for content


Design site

Write bios

Translate bios

PM

CO

PM [25%]

DD DD

TC, TJ, OC

PM, TC, TJ

PM PM

DD

TC, TJ

PM, DD, CO

PM, TC, TJ

CO

PM


CO


Write other texts


Draw diagram

Enhance diagram

Code site

Integrate content

Create Wiki

Translate diagram


Call for content


Design site

Write bios

Translate bios

PM

CO

PM [25%]

DD DD DD

TC, TJ, OC

PM, TC, TJ

PM PM

DD

TC, TJ

PM, DD, CO

PM, TC, TJ

CO

PM


CO


Write other texts


Draw diagram

Enhance diagram

Code site

Integrate content

Create Wiki

Test, debug, re-test site

Accept site

Translate diagram


Call for content


Design site

Deploy site

Close project

Write bios

Translate bios

PM

DD

CO

PM [25%]

PM, TC[25%], TJ[25%], DD

PM, TC, TJ, DD, CO

PM, CO DD DD DD

TC, TJ, OC

PM, TC, TJ

PM PM

DD

TC, TJ

PM, DD, CO

PM, TC, TJ

CO

PM


CO

Questions?

A plan using MS Project

(or ProjectLibre)

List of tasks (in MS Project)

List of tasks (in ProjectLibre)

Resource sheet (.mpp & .pod)

Gantt view (.mpp) – Resource assignment

Gantt view (.pod) – Resource assignment

Gantt view (.mpp) – Task sequencing

Gantt view (.pod) – Task sequencing

Gantt view (.mpp) – Complete plan

Gantt view (.pod) – Complete plan

Gantt view (.mpp) – Diagram

Gantt view (.pod) – Diagram

Resource usage (.mpp)

Resource usage (.pod)

Resource costs for project (.mpp & .pod)

Questions?

A plan using Excel

Project plan (with Excel) – List of tasks

Project plan – Resources & unit costs

Project plan – Durations

Project plan – Schedule

Project plan – Costs

Questions?

Risk analysis

Assumptions & risks - 1 Assumption: the site design needs to be reviewed and agreed

upon by both the PM and the developer, as well as by the

project owner.

Risk: none (there would have been a significant risk if these tasks had not been performed!).

The PM and the project owner should approve the design before development starts.

The PM and the project owner should also both validate the

website before it is opened to the public.

Assumption: 20 hours for design, 40 hours for coding, 16 hours for content integration, 32 hours for testing and bug

fixing, 4 hours for acceptance, 4 hours for deployment, etc.

Risk: these duration estimates may be optimistic or pessimistic.

Possible negative or positive impact on schedule

The risk is low because the assumptions are reasonable and the figures result from the cooperative requirements analysis

and discussion with the developer and other people involved.

Assumptions & risks - 2

Assumption: people supposed to provide content are available to do so.

Risk: people may not be available as expected.

Possible negative impact on schedule

The PM should…

check the actual availability of contributors,

make a call for content as early as possible, set a deadline for contributions and send reminders as necessary,

ask the project owner for help in motivating contributors to respond without delay,

make a provision for this risk in the schedule.


Assumption: a wiki needs to be installed to upload/download content; this should take 7 hours.

Risk: creating the wiki may take longer than planned.

Possible negative impact on schedule

The risk is low because the estimated duration of this task is based on experience.

If a wiki had not been created, some other mechanism for uploading/downloading content would have had to be set up.


Assumption: the use of a wiki to upload/download content does not present any problem as regards text in Chinese and

Japanese.

Risk: Chinese and Japanese text may be corrupted.

Negative impact on quality of content

A test should be performed with representative samples of Chinese and Japanese text.

If necessary, an alternative method should be devised for

sending content in Chinese and Japanese to the developer.


Assumption: the translators proofread their own translations.

Risk: translation errors and typos may be overlooked.

Possible negative impact on quality of content

With this particular project, the risk may be considered minor,

given the relatively small quantity of text and the quality of the persons involved.

As a rule, text should be reviewed by a qualified professional proofreader for each language.


Assumption: apart from proofreading, only one person (the PM) is involved full-time in the testing tasks, and there is only

one bug-fixing task.

Risk: some bugs may be overlooked or not fixed.

Negative impact on quality of website

With this particular project, the risk is very low, given the relative simplicity of the website.

As a rule, a website (or any other product) should be tested

(after "internal testing" by the developer) by more people than just the PM, and there should be more than a single sequence of "testing, bug-fixing, re-testing".


Questions?

pm - ganaxa case study & assignment - a project...

Documents