1/224
Looks like no tags are added yet.
Scope
All the work involved in creating the products of the project and the processes used to create them.
Deliverable
A product produced as part of a project, such as hardware or software, planning documents, or meeting minutes.
Project scope management
The processes involved in defining and controlling what is or is not included in a project, so the team and stakeholders share the same understanding of what will be produced and how.
Scope management processes
Planning scope management, collecting requirements, defining scope, creating the WBS, validating scope, and controlling scope.
Planning scope management
Determining how the project's scope and requirements will be managed. Outputs are the scope management plan and the requirements management plan.
Scope management plan contents
Prepare a detailed project scope statement, create a WBS, maintain and approve the WBS, obtain formal acceptance of completed deliverables, and control requests for changes to scope.
Requirement (PMBOK Sixth Edition)
A condition or capability that is necessary to be present in a product, service, or result to satisfy a business need.
Requirements management plan
Documents how requirements will be analyzed, documented, and managed: how to plan, track, and report requirements activities; do configuration management; prioritize requirements; use product metrics; and trace and capture requirement attributes.
Collecting requirements
Defining and documenting the features and functions of the project's products and the processes used to create them.
Ways to collect requirements
Interviewing stakeholders, focus groups and facilitated workshops, group creativity and decision-making techniques, questionnaires and surveys, observation studies, and benchmarking.
Requirements traceability matrix (RTM)
A table listing requirements, their attributes (e.g., name, category, source), and their status to ensure all requirements are addressed.
How Google Tests Software (best practice)
Describes how Google changed its culture so quality rests on those writing the code: don't rely on testers to ensure quality and don't believe in fads or buzzwords, including Agile.
Defining scope
Reviewing the project charter, requirements documents, and organizational process assets to create a scope statement.
Elements of a project scope statement
Product scope description, product user acceptance criteria, and detailed information on all project deliverables. Also helpful: project boundaries, constraints, assumptions, and supporting document references.
Scope clarity over time
As time progresses, the scope of a project should become more clear and specific.
Poor requirements management cost
For every dollar spent on projects and programs, 5.1 percent is wasted due to poor requirements management.
Work breakdown structure (WBS)
A deliverable-oriented grouping of the work involved in a project that defines its total scope. It is the foundation document for planning and managing schedules, costs, resources, and changes.
Decomposition
The main tool for creating a WBS: subdividing project deliverables into smaller pieces.
Work package
A task at the lowest level of the WBS.
Scope baseline
The approved project scope statement plus its associated WBS and WBS dictionary.
WBS development approaches
Using guidelines (e.g., U.S. DOD), the analogy approach, the top-down approach, the bottom-up approach, and mind mapping.
Analogy approach (WBS)
Reviewing the WBSs of similar projects and tailoring them to your project.
Top-down approach (WBS)
Starting with the largest items of the project and breaking them down.
Bottom-up approach (WBS)
Starting with the specific tasks and grouping them upward.
Mind mapping (WBS)
Using branches radiating out from a core idea to structure thoughts and ideas.
WBS dictionary
A document that describes detailed information about each WBS item, since many WBS tasks are vague. Its format can vary with project needs.
WBS and WBS dictionary advice
A unit of work appears in only one place; an item's content is the sum of the items below it; each item is the responsibility of one individual; team members help develop it; every item is documented in the dictionary; and the WBS stays flexible to changes.
Scope creep
The tendency for project scope to keep getting bigger and bigger.
Validating scope
Formalizing acceptance of the completed project deliverables, often through a customer inspection and then sign-off on key deliverables.
FoxMeyer Drug and McDonald's (scope failures)
FoxMeyer went bankrupt after scope creep and overemphasis on technology. McDonald's ended its 2001 real-time intranet project after spending $170 million on consultants and initial planning.
Controlling scope
Controlling changes to the project scope while keeping project goals and business strategy in mind. Goals: influence factors that cause changes, process changes by integrated change control procedures, and manage changes when they occur.
Variance
The difference between planned and actual performance.
Ways to improve user input
Insist sponsors come from the user organization, place users on the project team, hold regular meetings with defined agendas, deliver something regularly, don't over-promise, and locate users with the developers.
Ways to reduce incomplete and changing requirements
Follow a requirements management process, use prototyping, use case modeling, and JAD, keep requirements written and current, use a requirements database, test throughout, review changes from a systems perspective, emphasize completion dates, and allocate resources for change requests.
Software for scope management
Word processors for documents, spreadsheets and presentation software for charts and matrices, mind-mapping software for the WBS, communication software, project management software for the WBS and Gantt chart, and specialized software.
Scope in agile/adaptive environments
Stakeholders define and approve detailed scope before each iteration, producing a usable product at the end of each. Detailed scope develops over time.
Importance of project schedules
Delivering on time is a top challenge. Time has the least flexibility because it passes no matter what happens, and schedule issues are the main source of conflict, especially in the second half of projects.
Work styles and schedule conflicts
The Myers-Briggs J vs. P dimension reflects attitudes toward structure and deadlines. Cultures and countries also differ in their attitudes about schedules.
Project time management processes
Planning schedule management, defining activities, sequencing activities, estimating activity resources, estimating activity durations, developing the schedule, and controlling the schedule.
Planning schedule management
Determining the policies, procedures, and documentation for planning, executing, and controlling the project schedule.
Schedule management plan contents
Project schedule model development, scheduling methodology, level of accuracy and units of measure, control thresholds, rules of performance measurement, reporting formats, and process descriptions.
Defining activities
Identifying the specific activities team members and stakeholders must perform to produce the project deliverables.
Activity (task)
An element of work normally found on the WBS that has an expected duration, a cost, and resource requirements.
Activity list
A tabulation of activities to be included on the schedule, with each activity's name, identifier or number, and brief description.
Activity attributes
More information about an activity: predecessors, successors, logical relationships, leads and lags, resource requirements, constraints, imposed dates, and assumptions.
Milestone
A significant event that normally has no duration. It often takes several activities to complete one, and milestones help set schedule goals and monitor progress (e.g., customer sign-off).
FBI Trilogy project
A failed FBI system hurt by poor time management, missed milestones, and escalating costs. Sentinel replaced it in 2007 and still wasn't working well in 2014.
Sequencing activities
Identifying and documenting the relationships between project activities by reviewing activities and determining dependencies.
Dependency (relationship)
The sequencing of project activities or tasks. You must determine dependencies to use critical path analysis.
Mandatory dependency
Inherent in the nature of the work being performed. Sometimes called hard logic.
Discretionary dependency
Defined by the project team. Sometimes called soft logic, and should be used with care since it may limit later scheduling options.
External dependency
A relationship between project and non-project activities.
Network diagram
A schematic display of the logical relationships among, or sequencing of, project activities. It is the preferred technique for showing activity sequencing.
Arrow diagramming method (ADM)
Also called activity-on-arrow (AOA). Activities are arrows, nodes (circles) are start and end points, and it can show only finish-to-start dependencies.
Burst and merge (AOA diagrams)
A burst occurs when a single node is followed by two or more activities. A merge occurs when two or more nodes precede a single node.
AOA drawing rules of thumb
Work left to right, all arrowheads face right, and no arrows cross.
Precedence diagramming method (PDM)
Activities are boxes and arrows show relationships. It is more popular than ADM, is used by project management software, and is better at showing different dependency types.
Finish-to-start (FS)
Task B cannot start until task A finishes.
Start-to-start (SS)
Task B cannot start until task A starts.
Finish-to-finish (FF)
Task B cannot finish until task A finishes.
Start-to-finish (SF)
Task B cannot finish until task A starts.
Estimating activity resources
Estimating how many resources (people, equipment, materials) the team should use for each activity, considering difficulty, the organization's history, and resource availability.
Resource breakdown structure
A hierarchical structure that identifies the project's resources by category and type.
Duration vs. effort
Duration is the actual time worked on an activity plus elapsed time. Effort is the number of workdays or work hours required to complete a task. Effort does not normally equal duration.
Three-point estimate
An estimate with optimistic, most likely, and pessimistic values (e.g., 3, 4, and 5 weeks). It is needed for PERT and Monte Carlo simulations.
Developing the schedule
Using the other time management processes to determine project start and end dates and create a realistic schedule for monitoring progress. Tools: Gantt charts, critical path analysis, critical chain scheduling, and PERT.
Gantt chart
A standard format for showing project activities and their start and finish dates in a calendar format.
Gantt chart symbols
A black diamond is a milestone, thick black bars are summary tasks, lighter horizontal bars are task durations, and arrows are dependencies.
Adding milestones to Gantt charts
Enter a task with zero duration, or mark any task as a milestone, to emphasize important events or accomplishments.
SMART criteria (milestones)
Milestones should be Specific, Measurable, Assignable, Realistic, and Time-framed.
20-second rule (Shawn Anchor)
From The Happiness Advantage: people take the path of least resistance, so make distractions harder by adding time to them (e.g., keep email and websites closed while working).
Tracking Gantt chart
A schedule comparison chart showing planned dates against actual dates, including slipped milestones.
Critical path method (CPM)
A network diagramming technique used to predict total project duration.
Critical path
The longest path through the network diagram. It determines the earliest time the project can be completed and has the least slack or float.
Slack (float)
The amount of time an activity may be delayed without delaying a succeeding activity or the project finish date.
Calculating the critical path
Develop a good network diagram, add the durations on each path, and the longest path is critical. If a critical activity runs late, the project slips unless corrective action is taken.
Critical path facts
It is not the path with all the critical activities (it only accounts for time), there can be more than one if paths tie, and it can change as the project progresses.
Free slack (free float)
The time an activity can be delayed without delaying the early start of any immediately following activity.
Total slack (total float)
The time an activity can be delayed from its early start without delaying the planned project finish date.
Forward pass and backward pass
A forward pass through the network diagram determines early start and finish dates. A backward pass determines late start and finish dates.
Techniques for shortening a schedule
Shorten critical activity durations (add resources or change scope), crash, and fast track.
Crashing
Obtaining the greatest amount of schedule compression for the least incremental cost.
Fast tracking
Doing activities in parallel or overlapping them.
Updating critical path data
Update schedule information regularly because the critical path may change as actual dates are entered. If completion will slip, negotiate with the project sponsor.
Critical chain scheduling
A scheduling method that considers limited resources and uses buffers to protect the completion date.
Theory of Constraints (TOC)
A management philosophy developed by Eliyahu M. Goldratt and introduced in his book The Goal. It underlies critical chain scheduling.
Multitasking
When a resource works on more than one task at a time. Critical chain scheduling tries to minimize it.
Buffer
Additional time to complete a task.
Murphy's Law
If something can go wrong, it will.
Parkinson's Law
Work expands to fill the time allowed.
Project buffer and feeding buffers
Critical chain removes buffers from individual tasks. A project buffer is extra time added before the project's due date, and feeding buffers are extra time added before tasks on the critical path.
Program Evaluation and Review Technique (PERT)
A network analysis technique for estimating duration when individual activity estimates are highly uncertain. It uses probabilistic time estimates (optimistic, most likely, pessimistic).
PERT weighted average formula
(Optimistic time + 4 x most likely time + pessimistic time) / 6. Example: (8 + 4 x 10 + 24) / 6 = 12 days.
Agile and time management
Agile values customer collaboration over contract negotiation and responding to change over following a plan. The product owner defines and prioritizes work within a sprint, and not all work is defined before scheduling.
Schedule control suggestions
Perform reality checks, allow for contingencies, don't plan for 100% capacity all the time, and hold progress meetings with stakeholders with clear, honest communication.
Controlling the schedule
Knowing schedule status, influencing causes of change, determining that the schedule changed, and managing changes. Tools: progress reports, a schedule change control system, PM software (tracking Gantt), variance analysis, and earned value.
Reality checks on scheduling
Review the draft schedule or completion date in the charter, prepare a detailed schedule with the team, make sure it is realistic and followed, and alert top management early about problems.
People issues in scheduling
Strong leadership helps projects succeed more than good PERT charts. Project managers should use empowerment, incentives, discipline, and negotiation.
Cautions on project management software
Many people misuse it from lack of training. You must enter dependencies for dates to adjust and the critical path to be found, and enter actual schedule information to compare planned and actual progress.
Project cost management
The processes required to ensure the project is completed within an approved budget.