Project Plan by yaosaigeng

VIEWS: 70 PAGES: 8

									                                           LAWNSHARKS

                          LAWNSHARK V1.0 PROJECT PLAN



ABSTRACT     This document describes LawnSharks’ plan to deliver LawnShark v1.0.


REVISION HISTORY
Edition       Date                      Author                             Comments
           October 11,
  01                          Tammy Onufreiczuk        Initial Release
              2010




DOCUMENT TITLE:          LawnShark v1.0 Project Plan

EDITION                  01                                                        PAGE:   1/8
                                                                TABLE OF CONTENTS

1     SCOPE............................................................................................................................................................ 3

2     RELEASE OVERVIEW ................................................................................................................................ 3
    2.1      FEATURES ................................................................................................................................................... 3
3     SCHEDULE ...................................................................................................................................................... 4

4     PROJECT ORGANIZATION ....................................................................................................................... 5

5     PROJECT TOOLS ........................................................................................................................................... 5

6     COMPUTING RESOURCES ....................................................................................................................... 6

7     TRAINING ...................................................................................................................................................... 6

8     COMMUNICATION PLAN ........................................................................................................................... 6
    8.1      MEETINGS ................................................................................................................................................ 6
    8.2      REPORTING .............................................................................................................................................. 6
9     ACTION/ISSUE MANAGEMENT ..................................................................................................................... 7

10        DEFECT MANAGEMENT ..........................................................ERROR! BOOKMARK NOT DEFINED.5

11        CHANGE MANAGEMENT ........................................................................................................................... 7

12        MEASUREMENT PLAN........................................................................................................................... 8

13        DATA AND CONFIGURATION MANAGEMENT .....................ERROR! BOOKMARK NOT DEFINED.7




DOCUMENT TITLE:                      LawnShark v1.0 Project Plan

EDITION                              01                                                                                            PAGE:           2/8
1 SCOPE
      This document covers all project activities. This document is baselined at the project start.
      Changes will be made, as appropriate, at each project milestone.

2 RELEASE OVERVIEW
      LawnShark v1.0 is a web-based application targeted to clients operating home-based lawn
      servicing businesses. LawnShark v1.0 will help simplify customer/lawn account management
      and lawn service scheduling.

2.1   FEATURES
             Customer information management
             Lawn information management
             Appointment scheduling assistance based on lawn location, services, and day/time
              preferences
             Appointment rescheduling assistance
             Customer account balance tracking
             Customer payment tracking
             Support for check, cash, credit card and bill pay payments
             Overdue customer account report generation
             Customer retention report generation (to aid in sending service reminders)
             Daily lawn service schedule generation
             Add/modify/delete lawn services and parameters
             Smart phone application support
                  o   iPhone support
                  o   Remote crew appointment generation and assistance
                  o   Remote
                  o   Functionality for crew to take lawn notes
                  o   Functionality for crew to send notification if check or cash payment was made
                      at the time of service
                  o   Customer information display
                  o   Lawn information display




DOCUMENT TITLE:       LawnShark v1.0 Project Plan

EDITION               01                                                     PAGE:    3/8
3 SCHEDULE
       The project team members provide estimates of the work required for different tasks. The
       project scheduler uses the estimates to develop an integrated schedule. The team members
       review and approve the schedule, then the schedule is baselined at the project start. Any
       changes to the work effort or duration after the schedule is baselined are documented in the
       schedule.
       Refer to the embedded Microsoft Project Plan (mpp) Schedule below for the detailed project
       schedule.



            LawnSharks.mpp


       See the following figure for a timeline of the schedule.

  LawnShark v1.0 Timeline
                                                                              Today




     8/30         9/6           9/13        9/20      9/27       10/4         10/11        10/18       10/25          11/1         11/8         11/15           11/22        11/29          12/6


                8/30 - 9/13                                      9/30 - 10/11
            Problem Statement                                  Project Proposal




                                       9/14 - 9/24
                                       Use Cases

                                                9/21 - 9/27           10/5 - 10/11                  10/20 - 10/26
                                   9/14 - 9/20   Web App,              Web App,       10/15 - 10/18  iPhone App,
                                  Requirements Arch & Design        Implementation     iPhone App, Implementation
                                                                                      Arch & Design




                                                                           10/5 - 10/18              10/19 - 11/1
                                                                        Web App, Test Plan         Web App, Testing
                                                                                                                                 11/5 - 11/11   11/12 - 11/18
                                                                                                                                 iPhone App,     Integration            11/26 - 11/29
                                                                                                                                   Testing         Testing                Release
                                                                                                                                                                           Notes



                                                                                                            10/22 - 11/4                                   11/19 - 11/25
                                                                                                       iPhone App, Test Plan                                 Bug fixes
                                                                                                                                                                                     11/30 - 12/6
                                                                                                                                                                                       Prepare
                                                                                                                                                                                                     12/6
                                                                                                                                                                                     Presentation
                                                                                                                                                                                                    Present
                                                                                                                                                                                                    Project


                                                                                                                             10/20 - 11/23
                                                                                                                              User Docs




DOCUMENT TITLE:                        LawnShark v1.0 Project Plan

EDITION                                01                                                                                                           PAGE:                4/8
4 PROJECT ORGANIZATION
       The following table identifies the project team members and areas of responsibility.


Name and Contact Information                Roles
Joey Hardy                                     Design core libraries, write code and unit tests
281-615-3511                                   Design new features, write code and unit tests
hardythedrummer@gmail.com
Cale Sherry                                    Define database schemas and persistence layers
214-797-2812                                   Design core libraries, write code and unit tests
calesherry@gmail.com                           Share expert knowledge of iPhone development
Nara Guduru                                    Document system requirements
510-725-9459                                   Document system architecture
njugini@yahoo.com                              Review code changes and provide constructive
njugini@gmail.com                               feedback
                                               Design new features, write code and unit tests
Brad Havard                                    Test the system before each release
713-907-9918                                   Set up and maintain build tools and test automation
bradhav@student.utdallas.edu                   Review code for security and scalability
bradhav25@gmail.com
Tammy Onufreiczuk                              Manage project planning and scheduling
972-679-3148                                   Document use cases
tammymo@gmail.com                              Write end-user documentation
                                               Document our development process
                                               Design new features, write code and unit tests



5 PROJECT TOOLS
       The following is a list of tools required for the project:
                 Visual Studio 2010
                 Tortoise SVN
                 iOS Developer SDK 4.1
                 .NET 4.0
                 Xcode
                 Need testing tools




 DOCUMENT TITLE:          LawnShark v1.0 Project Plan

 EDITION                  01                                                   PAGE:    5/8
6     COMPUTING RESOURCES
       The following is a list of computing resources required for the project:
              Windows Server 2008
              SQL Server 2008
              IIS 7
              Apple OSX 10.6
              Apple iOS Device

7     TRAINING
       The following links provide training information for the project:
              http://www.asp.net/mvc
              http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-part-1.aspx
              http://msdn.microsoft.com/en-us/data/ee712907.aspx
              http://msdn.microsoft.com/en-us/netframework/default.aspx
              http://learn.iis.net/
              http://developer.apple.com/devcenter/ios/index.action
              http://proquest.safaribooksonline.com.libproxy.utdallas.edu/

8     COMMUNICATION PLAN
       This section describes the process for project communications and information distribution.

8.1    MEETINGS
       Team members will interface through routinely scheduled meetings, non-periodic/subject
       specific meetings, and informal contact.
       The team will have a weekly meetings for the duration of the project on Mondays at
       8:15 p.m. in ECSS 2.205 (unless otherwise specified for a particular week) to track progress
       of the project and to serve as a forum to resolve issues. Each meeting will have minutes.

8.2    REPORTING
       The project web page at http://code.google.com/p/lawnsharks/ will be used for status
       reporting information. The web page provides project status information (project schedule
       will be posted and updated), project documentation, source code access, issue
       reporting/tracking, training information.




DOCUMENT TITLE:        LawnShark v1.0 Project Plan

EDITION                01                                                     PAGE:   6/8
9 DEFECT/ISSUE MANAGEMENT
      The project web page provides the mechanism to identify, analyze, respond to, resolve, and
      close project defects and issues. As defects and issues are identified, they will be added to
      the issues register on the project web page. Each issue in the register has a description
      explaining the defect or issue and is assigned an ID, a type, an initial status of new, and an
      owner. Optionally, a low, medium, high, or critical priority can be assigned.
      The following table identifies the available issue types:




      The following table identifies issue status types as the issue progresses toward closure:




      The weekly team meetings will include a review of open defects and issues.

10    CHANGE MANAGEMENT
      Change management is used to track and control changes within a project. A change to the
      project is requested by opening an issue, via the project web page, with type Enhancement
      or Feature. Change management covers the following:
               Change Tracking
                 Change Evaluation
                 Change Approval
                 Change Implementation
      At the highest level, the change request management process is separated into two main
      phases:
                 Change Review Phase – review and analysis of a change request
                 Change Implementation Phase – project plan updated or created for the change
                  request
      The project team will review reqeusted changes during the weekly team meetings.

DOCUMENT TITLE:      LawnShark v1.0 Project Plan

EDITION              01                                                      PAGE:    7/8
11 MEASUREMENT PLAN
      The Schedule Performance Index (SPI) will be tracked for the project. The target SPI is
      between 0.8 and 1.2. Input data will be derived from baseline and actual data in the project
      schedule.

                                   END OF DOCUMENT




DOCUMENT TITLE:      LawnShark v1.0 Project Plan

EDITION              01                                                      PAGE:     8/8

								
To top