Tag: A – Z of Project Management
-
A – Z of Project Management : (B) Part 1
B1: BACKLOG A backlog is simply a build-up of unfinished work. Backlogs can affect numerous business units within a business and can be a regular part of discussions in the finance, accounting and administration type roles. When it comes to project delivery, backlogs have the potential to delay phase completion and ultimately scheduled go live
-
A – Z of Project Management : (A) Part 4
A21: ASSUMPTIONS Assumptions in the project management domain are contained within the RAID log which contains all the Risks, Assumptions, Issues and Dependencies for each project. They are normally tracked together, with Risks and Issues given greater weighting within a project. Assumptions should contain anything at the beginning of any given project that can be
-
A – Z of Project Management : (A) Part 3
A12: AGILE Agile is a project methodology that is lean by nature and is suited to small and medium software deployments of less than six months. They can be scaled up but this is less common. The agile development itself tends to run for two to three months and is broken down into SPRINTS that
-
A – Z of Project Management : (A) Part 2
A7: ACTIVITY SEQUENCING When planning out a project, step one will normally be to list down all the tasks you believe are needed to deliver a successful project. Obviously, task lists are completed at a particular point of time and will be what a project manager believes are all the tasks needed. But logic will
-
A – Z of Project Management : (A) Part 1
A1: ABSORPTION RATE For the purposes of Project Management, I will keep the definition simple and not aligned with the technical accounting definition. In projects there will always be costs that cannot be recouped from clients or business units internally. An example can be the easiest way to explain it. If the budget for a
my easy projects 