SCENARIO and OBJECTIVE OF THE PROJECT PLAN - SOFTWARE DEVELOPMENT PLAN

Scenario:
You are the Project Manager of a Software Product company.

- You have been tasked by the VP of Software Development to develop a new piece of software that will align with your flagship product.
- The key STAKEHOLDER of this project will be your own company. Before it is in production, training has to be provided also.
- After carefully considering you have chosen to adopt from CLASSIC WATERFALL software development methodology
- Software needs to be thoroughly tested - and conform to high quality standards
- Future maintenance of the project will be your responsibility - so carry no (or minimal) technical debt

Some guidelines you have established:
- You will establish Scope upfront
- Plan your requirements as meticulously as possible upfront
- Ensure a high quality outcome - by incorporating extensive testing through out the project
- There should be a Pilot Phase - which will deploy to a test environment - and also solicit feedback
- Separate Production environment deployment should be carried out

-------------------------------------------------

DESCRIPTION:
Exercise: 4 - SOFTWARE DEVELOPMENT PLAN
Complexity: INTERMEDIATE Level
Task Items: <~99 / ~6 months
File Type: Template inheritance
Domain: Technology
Project Management Phases: Initiation, Planning, Execution
Key Concepts Learned: Templates, Overallocations, Project Execution, Tracking, Baselines

-------------------------------------------------
The WBS / Task list

- We will be using the "Template" technique - we will use a standard template provided by Microsoft
- You can create your own templates similarly - and use it for running future projects.
- Templates are also used to enforce quality and standards