Organization of People and Resources
Dear Julianne, thank you for trusting me, I will shortly summarize few important things, hoping that I could answer all you questions and could contribute to your project’s success.
I do believe that every project is exceptional and a unique experience, as it things will not happen again “under the same set of circumstances” (Wysocki, 2009, p. xIi).
1.) As we both know from our experience one of the most challenging task is organizing human resources. It is essential that early in the planning phase the resources needed throughout the project life cycle are clearly known and identified. Just as you developed your projects’ work breakdown schedule, a resource breakdown schedule can be prepared to assist you in estimating the needed resources, and request them on time. In the field of software development, is utmost important to get the right professionals on your project, but we have experienced that often the project manager has no power to freely choose his/her project team members, but gets only the ‘available’ staff. In order to ensure that every selected team member understands his/her role and responsibilities, you can use the RAM/RACI matrix which I believe is a straightforward tool and will assist you in avoiding confusion throughout your scheduled activities, as the role of Responsible, Accountable, Consulted, Informed will be clearly understandable for each involved.
2.) The project scope statement (PSS) “states what needs to be accomplished by the project: product and work to generate the product” (Sanghera, 2010, p. 94). The PSS, as a guide for the project team and the stakeholders, will be looked into, and serve as a reference when a change request is submitted, and this will be used to prepare the work breakdown schedule. The PSS includes the deliverables and requirements to produce these deliverables or outcomes, but also has to comprise project assumptions and constrains. The project exclusions, what outside of the scope at the given stage has
I do believe that every project is exceptional and a unique experience, as it things will not happen again “under the same set of circumstances” (Wysocki, 2009, p. xIi).
1.) As we both know from our experience one of the most challenging task is organizing human resources. It is essential that early in the planning phase the resources needed throughout the project life cycle are clearly known and identified. Just as you developed your projects’ work breakdown schedule, a resource breakdown schedule can be prepared to assist you in estimating the needed resources, and request them on time. In the field of software development, is utmost important to get the right professionals on your project, but we have experienced that often the project manager has no power to freely choose his/her project team members, but gets only the ‘available’ staff. In order to ensure that every selected team member understands his/her role and responsibilities, you can use the RAM/RACI matrix which I believe is a straightforward tool and will assist you in avoiding confusion throughout your scheduled activities, as the role of Responsible, Accountable, Consulted, Informed will be clearly understandable for each involved.
2.) The project scope statement (PSS) “states what needs to be accomplished by the project: product and work to generate the product” (Sanghera, 2010, p. 94). The PSS, as a guide for the project team and the stakeholders, will be looked into, and serve as a reference when a change request is submitted, and this will be used to prepare the work breakdown schedule. The PSS includes the deliverables and requirements to produce these deliverables or outcomes, but also has to comprise project assumptions and constrains. The project exclusions, what outside of the scope at the given stage has