In project management for Software, there is a so called W5HH principle, to use for ensure that you cover the project rationale in a well though way.
- Why is the system being developed?
- What will be done by When?
- Who is responsible for a function?
- Where are they organizationally located?
- How will the job be done technically and managerially?
- How much of each resource is needed?
WHY IS THE SYSTEM BEING DEVELOPED?
Enable the parties to assess the validity of business reasons for the software. It justifies the expenditure of people, time, and money.
WHAT WILL BE DONE?
Specify the task set required for the project.
WHEN WILL IT BE DONE?
Determines the project schedule. Supports determining when tasks are conducted and when milestones are reached.
WHO IS RESPONSIBLE FOR A FUNCTION?
Accomplishing the role and responsibilities of each member of the software team.
WHERE ARE THEY ORGANIZATIONALLY LOCATED?
The software team does not contain all the roles and responsibilities. The customers, users and stakeholders also have responsibilities.
HOW WILL THE JOB BE DONE TECHNICALLY AND MANAGERIALLY?
Management and technical strategy of project is defined, once the scope of the product is established.
HOW MUCH OF EACH RESOURCE IS NEEDED?
Supports in deriving estimates, based on the answers to the above questions.
Read more on the topic here; https://study.com/academy/lesson/the-w5hh-principle-in-software-project-management-definition-examples.html
Also worth to look at Zachman Enterprise Framework, which have similar way to ensure that perspectives are covered.<< Back to list all models