Flowers North

Development of a

Web Site and Online Store

for

Outline of Orlene’s Discussion

• Background of Flowers North

• Business Needs

• Project Objectives (scope/schedule/cost)

• Not in Scope

• Assumptions

Background

• Flower and gift shop in Yellowknife, NWT

• Run by a single proprietor; she has two employees who work on a casual basis

• Orders are currently phoned or faxed in to store

• Also many inquiries about flower and plant care

Business Needs

The business needs to:

• Increase revenues through more sales by expanding customer base

• Make store accessible to Internet users

• Make it less costly for customers to send orders to the store

• Speed up the process of sending and receiving orders

• Reduce errors by not having to handwrite info

Project Objective

Purpose of developing the website:

• So customers can have the option of ordering flower arrangements, funeral wreaths, tropical trees and plants online instead of phoning or faxing in their orders

• So customers can access information pages about flower and plant care

Project Objectives (con’t)

• Cost– will utilize resources of 3 programmers– total cost is approximately $ 78, 800

• $68, 800 for labour

• $10, 000 for Hardware & Software

• Schedule– will be completed and delivered within 4

months from signing the contract

Project Objectives (con’t)

• Scope

- hardware and software procurement

- database that contains information about

products, orders and customers

- online catalogue/shopping basket

- order form for customers to enter required info

- manuals for administration/training purposes

- maintenance screens for administrator

Project Objectives (con’t)

• The Scope will not include:

- marketing the web site

- setting up a newsletter, chat room, forum

- tracking orders

- testing by a security firm

- researching banks/web site hosting

- maintaining site after fully operational

Assumptions

- expansion limited to local area

- web site hosting will be local

- target platform is Windows-based

- owner/employees available for meetings

- access to existing documents/forms/info

- not responsible for accounting system

Outline of Jayd’s Discussion

• Work Breakdown Structure

• List of Activities

• Schedule Table

Work Breakdown Structure

Definition:

• A hierarchical tree of activities that need to be accomplished to complete the project according to the project scope

• Groups related activities into packages

Work Breakdown Structure

1 A n a lys isO rle ne

2 D e s ignJa yd

3 D e ve lo p m e ntT a ra

4 T e s tingO rle ne

5 H a rd w a re /S o ftw a reP ro cu re m e ntJa yd

F lo w e rs N o rthW e b S ite

A ndO n lin e S to re

Work Breakdown Structure (con’t)

6 M an u a lsT a ra

7 Im p le m e n ta tionO rle ne

8 T e rm in a tionJa yd

9 M ee tin gs /M on th lyR e p o rtsT a ra

F lo w e rs N o rthW e b S ite

A ndO n lin e S to re

Detailed Work Breakdown Structure

3 .1 C re a te D a tab a sesT a ra

3 .2 C o d e W e lcom e /In fo P ag es

O rle ne

3 .3 C o d e O n lineO rd e r P a g es

T a ra

3 .4 C o d e A d m in is tra tio n /L o g in P a g es

Ja yd

3 D e ve lo p m e ntT a ra

7 .1 In s ta ll S ys tem &Im p lem e nt S ecu rity

Ja yd

7 .2 T es t H a rdw a re &S o ftw a re

Ja yd

7 .3 D a ta C o nve rs ionO rle ne

7 .4 T ra in ingT a ra

7 Im p le m e n ta tionO rle ne

F lo w e rs N o rthW e b S ite

A ndO n lin e S to re

Schedule Table

Phase Start Date End Date

Analysis Tue 01/02/2001 Wed 01/10/2001

Design Thu 01/11/2001 Wed 01/24/2001

Development Wed 01/24/2001 Thu 03/15/2001

Testing Thu 03/15/2001 Thu 03/22/2001

Hardware/Software Thu 03/22/2001 Wed 03/28/2001

Manuals Thu 03/22/2001 Thu 03/29/2001

Implementation Thu 03/29/2001 Mon 04/09/2001

Termination Mon 04/09/2001 Fri 04/13/2001

Meetings Throughout Throughout

Outline of Tara’s Discussion

• Network Diagram

• Critical Path

• Project Control

• Conclusion

Network Diagram Definition

• Shows the flow of activities in sequence

• Shows the relationships between activities

• Top-level network diagrams are similar to the work breakdown structure except that the flow of activities, and relationships between activities are not shown

Critical Path Definition

• Critical Path– Any path of activities with zero or

negative slack• i.e. activities with start/stop dates that

aren’t flexible

• The Most Critical Path– the most time-consuming path of

activities for a project

Network Diagram

Phase 1: Analysis

Phase 2: Design

Phase 2: Design (con’t)

Critical Path

Project Control

• Specific tasks– Assess risk (analysis phase)– Update risk profile (design phase)– Analyze/revise project scope– Preliminary/final design review meetings

Project Control (con’t)

• Periodic Tasks– Review/Approval/Signoff by Manager (client)

• Weekly Status Review Meetings (with project team) – Accomplishments– Status/Trends/Forecasts– Scope/Schedule/Cost Changes– Corrective Actions– Cost Performance Analysis

• Actual vs. Budgeted Cost

– Measure Actual Progress/Compare to Planned Progress– 1 hr each, 1 hr. together

Project Control (con’t)

• Monthly progress reports (sent out before review meetings

• Monthly status review meetings (with clients)– Same agenda as weekly status review meetings

Project Control (con’t)

• Problem Solving Meetings– On an informal/spontaneous basis– Small project—anyone can initiate

Conclusion

We have covered:

• A brief overview of our project plan

• Some of the phases in more detail

• How we plan to control the project so that it can be completed in time, on budget, and within scope.

Thank you!

Any questions?