Gary Neilson
"Overseas programmers could be a big problem if not properly managed..."
In Software Product development projects, Custom Software Project plan is both process and one of the core documents. Being created on the earliest stage of the Custom Software Project, the document is changed and refined during the overall Custom Software Project lifecycle according to the changing circumstances. In Software Development projects it helps not only to define activities, resources and costs, but also to assure mutual understanding of goals of the Custom Software Project.
Planning is aimed not only at planning resources and activities but also at agreeing estimates, goals and commitments among all stakeholders. It must be paid special attention in Software Development projects, because in such projects negotiation process is complicated by language, cultural and other barriers. Custom Software Project plan is also targeted to assure the Software Development provider’s ability to implement the Custom Software Project. It confirms the availability of proper statement of work, necessary resources and properly qualified personnel as well as assignation of responsibilities within an Software Development company and Customer’s company. Software Product development Custom Software Project planning begins with defining the statement of work and goals. The main disciplines in Custom Software Project planning are estimation of efforts (needed for planning, preparation, programming, testing, debugging and delivery), scheduling the Custom Software Project, definition and analysis of risks, and negotiation of commitments. Planning process results in a plan of the Custom Software Project (usually, Software Product development plan). Despite use of the phrase “Software Product development” in its name, the term “Software Product development plan” refers to the whole Custom Software Project, and is not limited to only construction phase. Statement of work is the basis for further planning activity. It is usually a separate document (SOW) covering business goals and needs of the Custom Software Project, its stakeholders (customer and end users), and defining the scope of the Custom Software Project. It also includes standards, resources, designation of responsibilities, schedule and budget. The document must be reviewed and agreed by all affected parties (Custom Software Project manager, Software Product manager, Customer, etc.).
Not only Custom Software Project managers are responsible for planning. Programming team participates in Custom Software Project planning from the first stages. Programming personnel must be involved in it on the earliest stages, estimation phase. The programming group participates in Custom Software Project planning process throughout the overall Custom Software Project, from estimation to testing, delivery and maintenance. Briefly, the activities performed while planning the Custom Software Project are the following:
1. Estimation and its negotiation
2. Involving of all affected parties (writing documents from one party; review and agreement from the other)
3. Review and negotiation of commitments
4. Definition of type of Software Product Custom Software Project (according to the chosen type, manageable stages of the Custom Software Project lifecycle are identified)
5. Documentation of Software Product development plan
6. Definition of project results
7. Measurement of Software Product products size
8. Estimation of Custom Software Project budget
9. Definition of needed computer and personnel resources
10. Documentation of project’s schedule
11. Risk analysis
12. Definition of needed facilities.
The Custom Software Project plan must be verified by all parties of the project including representatives of both Customer and Software Development company.
Published on 7/30/2007
