Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

Reflection #3

Based on the Project defining chapter 1st step is defining the project scope; the project scope is
the boundary of the project work, it can be the assigned budget for the project, or it can be the
resources allocated, technical support, etc.
Through a project scope statement, the boundary of the project is briefly defined to the project
team.
Based on the project scope statement project will be planned and the final outcome will be
measured, therefore project scope statement is very important for a project.
Next, the project charter consists of budgeted amounts, team composition, and other limits of the
project.
Scope creep is the next main document of a project scope, which is necessary when it is needed
for any expansion or change to the initial scope of the project.
2nd step is to establish project priorities, which are Cost, Time, and Performance(scope). To
succeed in a project there should be the perfect balance between these three criteria, and It will
create quality output for the customer.
These criteria can vary between three situations those are Constrain, Enhance, and Accept.
3rd Step is Creating a work breakdown Structure. As I understand, WBS provides a clear and
structured way to understand the project's scope and the relationships between its various
components.
4th step is building an OBS, which is a tool for project managers to align the project's structure
with the organizational structure and ensure that roles, responsibilities, and resources are clear
and well-defined.
Practically, OBs are not much used by interacting with WBS due to higher complexity.
5th step is coding WBS, which makes it easier to manage and track the project's progress, costs,
and other relevant project management information. Under coding WBS, we learned the
responsibility matrix, which clearly defines the responsibilities of each and everyone on the
project team. It will help teammates to get a clear understanding of their tasks. Moreover, we
discussed that a Project Communication Plan is like a map for a project. Stakeholder analysis
consists of a project communication plan which is very important for a project's success.
Finally, we learned the "RASI" model, which stands for Responsible, Accountable, Supportive,
and Informed, and it helps ensure that everyone involved in a project knows who is responsible
for what, who is accountable for the outcomes, who provides support, and who needs to be kept
in the loop.

You might also like