assignment 6

Project Scope Management (u01a1)

1.    Angela regarding project Overview (page 6) will be appropriate including project cost, project start date (mm/dd/yyyy), project completion date (mm/dd/yyyy) along with considering and briefly discussing project methodology that will be used/considered for the project planning along with software planning tools; being repetitive with stakeholders is not a bad idea to ensure important information is conveyed to project stakeholders.  

2.   Angela reconsider concisely stating within the Business Objectives what the project entails, what it will cost, and project start and target completion date (mm/dd/yyyy); it is important to reinforce communicating with stakeholders what the project entail; reaffirm project details, cost, start and end date

3.   Angela the project Scope is based on the project Charter (or business Objective statement)â��Charter reaffirmation in terms of cost, start and end dates, thus one of the key factors for the project Scope is to revise what the project entails ensuring the project is feasible, the cost is accurate as well as target project completion date; any revisions is fully document and presented to project Sponsor for approval.

4.   Angela will be appropriate further identifying key Charter project milestones (in assessment two you will be asked to develop WBS based on milestones):

a.   Consider focusing/identifying project Scope key milestones (actions to deploy Preventive Care system).

b.   Start milestone description with a noun (or verb) to clearly communicate with stakeholders what the milestone will accomplish.

c.   Refer to WBS example located under Word submitted (page # 6); evaluate/extrapolate appropriate milestones.

Assignment 2 evaluations

1.    Angela per previous feedback, regarding project overview (page 5) reconsider assessment 1 feedback given; include what the project will cost, start (mm/dd/yyyy), and end date (mm/dd/yyyy), project methodology; provide stakeholder a more comprehensive project overview prior to next submission (note: projects are finite); replace 180 day with project start and end date.

2.   Angela regarding project Business Objectives (word page #5) consider in addition to stating what the entails, include what the project will cost, start and end target completion date (mm/dd/yyyy); refer to assessment 1 feedback; itâ��s not a bad idea to reinforce key project information to stakeholders.

3.   Angela reconsider developing a more comprehensive WBS; best approach is being more descriptive as to what the milestone and milestone will accomplish:

a.    Use noun (or verb) to fully describe what the activity will accomplishâ��be more descriptive.  

b.   As you revise WBS activities focusing on project Scope activities; develop a more comprehensive WBS.

c.    Consider that milestone tasks should be atomic (task can no longer be split further).

d.   Consider that WBS will be the basis from which the Gantt will be created later in the course.

e.   Consider revising WBS example located within the Word submitted page #8.

4.   Angela regarding project Logical Relationships consider focusing on project Scope objectives best approach explaining to project Stakeholders what project sequencing is about. Thus, addressing project sequencing (FS, SS, FF, and SF) discussion should be based on project WBS activities comprehensive WBS. Logical FS, SS, FF, and SF diagrams looks appropriate to better provide stakeholders a better understanding the importance of Logical Sequencing for the project; having a comprehensive understanding of the projectâ��s scope will give clues as to the most appropriate order (sequence activities) in which certain activities must be carried out.

a.    Consider creating a table to summarize pros and cons for each logical sequence. Regarding charts, best approach is to develop own charts.

b.   Reconsider creating FS, SS, FF, and SF custom diagram to support Logical Sequencing; educate project Stakeholders who may not be familiar with project Logical Sequencing process. Further consider addressing project logical sequencing based on project WBS milestones. Further, consider creating a table to summarize pros and cons for each logical sequence.