Fluent Essays

Reflect on the assigned readings for Week 4 and then type a two page paper regarding what you thought was the most important concept(s), method(s), term(s), and/or any other thing that you felt was worthy of your understanding. Define and describe what you thought was worthy of your understanding in half a page, and then explain why you felt it was important, how you will use it, and/or how important it is in project planning. After submitting your two page paper as an initial post in the Reflection and Discussion Forum,400 words, APA format and I have attached the readings. chapter_10_project_schedule_planning.pptx chapter_9_scope_planning.pptx Unformatted Attachment Preview Project Schedule Planning This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning • • • • • The Project Schedule Defining Activities Case study of WBS development Activity definition and Task dependencies Leads and lags . . . continued on next slide This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning (continued) • • • • • Milestones Activity Sequencing Gantt Chart Network Diagram Critical Path This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning The Project Schedule • A project schedule includes • the sequence of activities, • the duration planned for each activity, and • relationships or dependencies between the beginnings and ends of different activities. • The project schedule is created • AFTER the scope planning has created the WBS • BEFORE project resource planning This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Review: Scope Planning • WBS breaks down the deliverables into smaller units, ending with the work packages. • A work package is a clearly defined activity or group of activities whose duration can be estimated. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Case Study: Wedding Deliverables This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Deliverables Decompose into Work Packages • • • • • • Shop for shoes Create guest list Tailoring and fitting Shop for dress Find caterer Cater the wedding • Print the invitations • Choose the bouquet • Wait for RSVPs • Mail the invitations • Finalize the menu This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Case Study: Wedding Deliverables This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Remember • WBS follows 100\% rule • There is no sequencing of tasks in the WBS This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Task Dependencies • Finish-to-start This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Task Dependencies • Start-to-start This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Task Dependencies • Finish-to-finish This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Types of predecessors • External predecessors • Outside the project, such as the previous party being out of the reception hall • Discretionary predecessors • Matter of preference: bridesmaids arrive before couple • Mandatory predecessors • Cannot do the following task until the predecessor is done: invitations must be addressed before they can be mailed This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Leads and Lags • Lag: One task must wait in relation to another task: This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Leads and Lags • Lead: The task must start before the predecessor is done: This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Milestones • A milestone is an important checkpoint—usually completion of a major task or a major set of tasks. • Target dates will be set later This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Milestones in Wedding Plan • • • • Invitations Sent Menu Finalized Location booked Bridesmaids’ dresses fitted This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Creating a Gantt Chart • Gantt Chart is a horizontal bar chart with a list of activities on the left and a timeline on the horizontal axis. • A traditional Gantt chart does not show dependencies; many current Gantt charts add the critical path and arrows to indicate tasks that precede other tasks. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Gantt Chart for Wedding Plan This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Network Diagram • • • • Also known as PERT chart or PERT/CPM chart Illustrates task relationships Used to determine the critical path Software such as Microsoft Project can be used to create a network diagram. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Network Diagram for Wedding This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Network Diagram: Activity on Arrow • Alternative method • More difficult to read and understand • May require the creation of dummy activities when a task has multiple predecessors and multiple dependent tasks • More “mathematical” in its illustration of activities and events. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning The critical path • When multiple paths exist through the network diagram, the path with the longest duration is called the critical path • If any task on the critical path is delayed, the project is delayed • Tasks NOT on the critical path have slack available. This is the amount of time the task could be delayed without delaying the completion of the project This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Critical Path Example This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Critical Path Example In this example the critical path is A,B,C,D,E,F,I,L, and the earliest completion date for the project is the sum of the estimated times for all the stages on the critical path – 28 weeks This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Slack • Slack is the amount of time a task could be delayed without delaying the completion of the project • Tasks on the critical path have zero slack • For tasks NOT on the critical path, work backwards from the project duration to determine the amount of slack This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Slack on Critical Path Example In this example the slack for task K is 2 weeks. If task K is delayed by less than two weeks, it will not delay the completion date of the project. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Types of Slack • Total Slack • Allowable delay of an activity without delaying project completion (usual meaning of “Slack” if not specified) • Free Slack • Allowable delay of an activity without affecting the earliest start of any dependent (following) activity • Safety Slack • Remaining allowable delay of an activity if all predecessors finish as late as possible This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Network Diagram compared to Gantt • Network diagram is more technical, helps determine the critical path • Network diagram is not to a scaled timeline • Gantt is easy to read and explain to non-technical people • Gantt has a good method for graphically illustrating task progress and whether things are ahead of schedule or behind This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Network Diagram compared to Gantt • Project managers depend on network diagram to plan and to adjust • Gantt is developed from network diagram for purposes of communicating the plan • Both are easily produced from project management software This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Finalizing the Project Schedule • May have to negotiate with sponsor or adjust customer expectations • Schedule will be impacted by Project Resource plans • Monitor the critical path tasks most closely This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning Summary • The Project Schedule shows when each activity will take place and the dependencies between activities • Activities or work packages are derived from the WBS, which was developed in Project Scope Planning • Task dependencies may be • • • • Finish to start Start to start Finish to finish Leads and lags . . . continued on next slide This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning Summary (continued) • Milestones are checkpoints • Activity Sequencing is determined by the dependencies • Gantt Chart is a horizontal timeline showing when each activity is scheduled, along with optional indicators of task progress • Network Diagram helps Project Managers illustrate task dependencies and determine the critical path . . . continued on next slide This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning Summary (continued) • Tasks on the critical path have no slack • If a critical path task is delayed, project completion will be delayed • Tasks not on the critical path have slack. • If a non-critical task is delayed by less than the slack, project completion will not be delayed. . . . continued on next slide This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Project Schedule Planning Summary (continued) • After the schedule is developed: • Get approval from sponsor; may require some negotiations • Next step will be to develop the project resource plan • Project Resource Planning may cause schedule adjustments This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Questions? This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 10: Project Schedule Planning Scope Planning This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Planning • • • • • • Defining the scope Project requirements Scope Inputs Requirements traceability matrix Work Breakdown Structure (WBS) Scope statement This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Project Scope • One of the main activities in the Project Planning phase is determining and documenting the project scope. • Project scope is the definition of all the work needed to successfully meet the project objectives. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Deliverables • Must be described in a sufficiently low level of details This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope • Be as specific as you can • Where possible, the scope statements should include how the results will be measured so you and your sponsor will know with certainty whether that part of the scope has been achieved • Requirements should tie to things like the organization’s strategic plan and business objectives • Mention things that are explicitly NOT included: is this limited to certain locations? If in an international context, is it in only one language? This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Not measurable Measurable A new registration system With the new system, students will be able to register for classes using a browser or a smartphone. The system will be fast Response time will be under 1 second The system will support the required volumes 75 students must be able to add an average of 3 classes each 15-minute period. Happy users User satisfaction will be measured by a standardized set of questions and will measure 5 or higher on a 7-point scale. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Types of requirements • Functional • Non-functional • Performance • Development • • • • Technical Business User Regulatory This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Software requirements fundamentals • Unique challenges • Must be verifiable This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Measuring requirements • Each type of requirement may require a different type of measure: This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope inputs-techniques • • • • • • Interviews Focus groups Facilitated groups– JAD, QFD Group creativity techniques such as brainstorming Prototyping Observation • Questionnaires and surveys This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Inputs-sources • • • • • • Project sponsor Management Strategic Plan Users Customers Competitors • Suppliers • Regulations • and others This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Requirements Traceability Matrix • Links requirements to their origin • Traces them throughout the project process • May link requirements to: • business needs, opportunities, goals, and objectives; • project objectives; • project scope/WBS deliverables; • product design; • product development; • test strategy and test scenarios; • or may link • High-level requirements to more detailed requirements. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Simplified Requirement Traceability Matrix Code Description Source Priority Status 5 User interface must comply to company standard Corporate IT standards manual 1 In-progress 5-1 Help text uses corporate fonts Corporate style 2 manual 8-6 Include the users in the Project Charter, 1 testing item 7 This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). complete Project Management Chapter 9: Scope Planning Requirements Traceability Matrix fields • • • • • • Unique identifier Requirement statement Source Design specification reference Test specification Test case numbers • Remarks • … and more depending on the particular situation This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation • List all the project outputs (deliverables and other direct results); • Identify of all the activities required to deliver the outputs. • Subdivide the activities into sub-activities and tasks. • Identify the deliverable and milestone(s) of each task This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS • A list of all activities required to create all the deliverables in the scope. • Activities may be broken down into smaller tasks, in a hierarchical pattern • Do not focus on sequence or dependencies at this point This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS • Follow a numbering plan • Can also be shown in outline format • May be very complex for a large project This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation Remember the 100\% Rule: The combination of the boxes on each level represent 100\% of the parent box. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation • At the lowest level, the WBS consists of Work Packages • It is important that each work package is clearly defined and can be easily assigned • The work package level is where time estimates, cost estimates and resource estimates are determined. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Statement • Purpose: • Project deliverables • Major objectives • Measurable success criteria • Create and use a template suitable to your organization This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Statement Typical Contents • Project Name • Project charter • Owner, sponsor, project manager, stakeholders • Problem statement • Project Goals and Objectives • Project Requirements • Project Deliverables • Exclusions • Milestones • Cost estimates This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Summary • Scope planning is an essential activity during the planning phase of the project • Provide relevant details and measurable deliverables in your scope • Use a Requi ... Purchase answer to see full attachment