1. Flowers North Development of a Web Site and Online Store for

2. Outline of Orlene’s Discussion Background of Flowers North Business Needs Project Objectives (scope/schedule/cost) Not in Scope Assumptions

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. Outline of Jayd’s Discussion Work Breakdown Structure List of Activities Schedule Table

11. 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

12. Work Breakdown Structure

13. Work Breakdown Structure (con’t)

14. Detailed Work Breakdown Structure

17. Schedule Table PhaseStart DateEnd Date AnalysisTue 01/02/2001Wed 01/10/2001 DesignThu 01/11/2001Wed 01/24/2001 DevelopmentWed 01/24/2001Thu 03/15/2001 TestingThu 03/15/2001Thu 03/22/2001 Hardware/SoftwareThu 03/22/2001Wed 03/28/2001 ManualsThu 03/22/2001Thu 03/29/2001 ImplementationThu 03/29/2001Mon 04/09/2001 TerminationMon 04/09/2001Fri 04/13/2001 MeetingsThroughout

18. Outline of Tara’s Discussion Network Diagram Critical Path Project Control Conclusion

19. 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

20. 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

21. Network Diagram

22. Phase 1: Analysis

23. Phase 2: Design

24. Phase 2: Design (con’t)

25. Critical Path

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

27. 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

28. 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

29. Project Control (con’t) Problem Solving Meetings –On an informal/spontaneous basis –Small project—anyone can initiate

30. 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.

31. Thank you! Any questions?