This chapter talked about formulation of the project management plan, a document that details how you're going to manage the project. Specifically, we talked about how you'll report to stakeholders. Communication is everything in good project management.
We also talked about tracking methods used in projects: by metrics, by cost, or by other variables. I discussed the project's schedule and how you'll handle it. Specifically, the deliverables will be accomplished by the completion of tasks. Many tasks combined together make up an activity. Many activities combined together make up a phase. Many phases make up the project. Tasks, activities, and phases have a specific duration assigned to them, the sum of which defines the overall expected length of the project. Tasks, activities, and phases can be represented in a variety of schedule- formatting mechanisms, but the most common is the one you'll find as the default in Microsoft Project, a combination of a spreadsheet that contains the task list (including duration, team members, predecessors, and successors) as well as a Gantt chart, which shows the duration of a task on a calendar with links to other tasks.
There are several interesting cost estimating techniques, but normally in IT projects we use bottom-up estimating. The idea is to start with the smallest costs first, then work your way up to the largest, taking into account salaries, equipment, contractors, and other items. Cost estimating is not budgeting, and your cost estimates will doubtless feed a budget mechanism of some kind, typically spread across a lot of budgetary cost centers. Quality management is highly important in any project of any size, though the quality techniques you utilize will not be as numerous in smaller projects as in bigger ones.
Checkpoints serve as a method where you stop to see what you' ve accomplished so far; the more numerous the checkpoints, the more likely you are to arrive at a finely tuned product, but the longer the product is going to take to conclude. Architectural control is assigned to technicians who understand the technology and recognize good design characteristics. Unit testing is the singular testing of a given phase' s, activity ' s, or task' s outcomes. Systems testing involves the entire in toto test of the completed system. User acceptance testing (UAT) involves asking users associated with the business to test the code to see if it meets their needs. Intermittent UAT throughout code development will result in more robust, rich code that more effectively meets user needs. Simulation software can stress-test systems that will encounter heavy usage.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.