Isabel Leverrier November 10, 2020 Project Management
The business requirements state what is required but do not specify how the deliverable will actually work. So in many projects with a tangible and technically sophisticated deliverable, it is very common to produce additional documentation about the look and feel of the end product. The functional specification describes not only how the end product will look but also how an end-user will actually use it and what the user-experience will be like. This document should contain sections that specifically relate to each of the requirements in the business requirements document so that every functional item can be tracked back to an original business need.
Most of us are beyond the point where we believe that successful project management can be accomplished by following a formula or merely using the right system. It is not that the tools are unimportant, or that the systems do not work, because they do. However, the systems and the software only make the job easier; they are not the elements of success.
Most team members often feel overwhelmed with the prospect of having to worry about timelines and tasks they need to accomplish over the duration of the work effort. Helping them to stay focused and organized is a key skill that a PM must bring to the table when running a project.
Then you bring in your techies to ask them to prepare a project scope document along with a report, in which the specific technologies and the steps to carry out the plan are decided. The scope and the feasibility of it are studied and a decision on whether to take it up or to pass on the offer is made. This official document contains everything from primary goals of the scheme to the deliverables expected of it. Once the document is perused and the upper management gives it a green signal, the project is considered as taken!
All projects have control points and required deadlines, where progress is monitored and measured. In the event that a deadline is missed then the overall impact on project completion time can be assessed, and if necessary new timetables drawn up, re-negotiated and agreed. Action Plans are lists of tasks/individual actions that are carried out to achieve a single and objective or outcome - in this case, the specific project. Action Plans focus on the achievement of a single goal, the action may then be translated in to a to-do list/diary cum calendar which cover many goals.
Regardless of terminology a company uses, the purpose of the WBS is to organize the project into various deliverables or summary reporting levels. Some of the traditional stage (or phase) levels in IS projects include project definition, analysis, design, development, testing, implementing, and project review. Whether a project has standard levels or not, the main purpose of these higher levels is to group the detail tasks, allowing project administrators to more easily track the project`s progress.