Project+ WGU D324

(Tracking Charts)

Budget Burndown Chart

shows how quickly we are burning through our budget

(Tracking Charts)

sprint burndown chart

amount of effort is remaining to do on a project vs the time left

(Tracking Charts)

Task Board (Kanban Board)

used to visually track the status of each task we are working on

each column is the state of the task

heading is the task

(Tracking Charts)

Gantt Chart

chart in which a series of horizontal lines shows the amount of work done or production completed in certain periods of time in relation to the amount planned for those periods

(Tracking Charts)

Project Network Diagram

a visual representation of the workflow of a project

(Tracking Charts)

PERT Chart

a graphical representation of a project's timeline that displays all of the individual tasks necessary to complete the project (finish to start FS etc.)

(Tracking Charts)

Milestone Chart

mark significant points in the schedule

(schedule overview for key steakholders)

(Tracking Charts)

Project Organization Chart

who reports to who.

shows the roles and reporting for the projects teams.

(Charts and Tools)

run chart

line chart plotting data over time

(Charts and Tools)

velocity chart

(an agile term (scrum))

the rate at which work is completed over time.

Shows how much work the team can complete in a sprint.

(Charts and Tools)

Story Points

a "story point" is the unit of measure for the estimate of the effort required to implement a product backlog item (or user story)

The point value assigned takes into account the estimated effort and complexity

(Charts and Tools)

Decision Tree

is a map of the possible outcomes of a series of related choices.

starts with a single node which branches out into possible outcomes.

(Charts and Tools)

Histogram

used for detecting defect types

(Charts and Tools)

Pareto chart

is like a histogram just shows the data sorted with a pareto line showing the cumulative total

it can show us which defect we should focus on fixing

(Charts and Tools)

scatter diagram

shows correlation between two variables

use to see if two variables are linked, which may indicate the cause of a problem

(Charts and Tools)

control chart

thresh holds

upper and lower control limits

(Charts and Tools)

Fishbone / Ishikawa diagram

cause and effect analysis

how to solve a problem

(Project Documents)

Business Case

A value proposition for a proposed project

Includes business needs, options, recommendations, feasibility study

(key purpose - should the project proceed?)

(Project Documents)

The Project Charter

provides high level information to define project objectives, set boundaries, align expectations, and describe success

(key purpose - authorize the project to begin)

(Project Documents)

Project Plan

defines how the project will be executed, monitored and controlled, and closed.

Contains a number of subsidiary plans, and baselines.

(key purpose - our guide on how we are going to manage the project)

(Project Documents)

Requirements Traceability Matrix (RTM)

When gathering requirements at the beginning of the project, we use the RTM to document who requested each requirement, what business justifications it aligns to, and which bits of the WBS it relates to (and more)

(Project Documents)

Risk Register

log all the outputs from out Risk Management activities

(Project Documents)

Risk Report

written document which summarizes information on individual project risks, and the level of overall project risk

(Project Documents)

Change Log

comprehensive list of changes submitted during the project, and their current status

(Project Documents)

Issue Log

record issues and track their status

(Project Documents)

Defect Log

record the results of inspections and tests

(Project Documents)

Status Report

written document summarizing project progress

It will be distributed to stakeholders according to the communication plan

(Procurement Documents)

NDA (non disclosure agreement)

agreement that is signed that states that trade secrets or sensitive information will not be shared outside of the organization

(Procurement Documents)

MSA (Master Service Agreement)

Umbrella agreement to set general terms between parties, which can help streamline future contracts

(Procurement Documents)

C&D Letter (Cease and Desist)

used to stop (cease) somebody doing something immediately and never do it again (desist)

(copywrite violation example)

(Procurement Documents)

LOI (Letter Of Intent)

describes the intention of what the buyer and vendor are going to do, usually before they enter into a contract

Not always legally binding, but can carry weight

(Procurement Documents)

SLA (Service Level Agreement)

Defines expectations of the level of service provided by the vendor

(Procurement Documents)

Maintenance Agreement

describes what the vendor is expected to do to in order keep the goods or service you purchased up and running

(Procurement Documents)

MOU (Memorandum Of Understanding)

Outlining terms when it's not possible to create a legal agreement between parties

(Procurement Documents)

SOW (Statement Of Work)

details of the services or goods we want to purchase, so that the vendor knows what we're asking them to provide

Similar to TOR

(Procurement Documents)

PO (Purchase Order)

The official document issued by a buyer committing to pay the vendor for the sale of the specified products or services

(Procurement Documents)

Warranty

The vendors guarantee that the product will perform as expected for a specified period of time

(Procurement Documents)

TOR (Terms Of Reference)

description of the work requirement including the scope, timeline, resources etc...

similar to SOW

what are some list of Software tools (7)

Word Processor

Spreadsheet

Presentation Program

Charting / Diagraming

Project Management Software

Time Tracking

Ticketing / Case Management

list of Communication and Collaboration Tools (6)

email -

Messaging (SMS/Chat) -

Telephone -

Face-to-Face Meetings -

Video Meetings -

Enterprise Social Media -

(Cloud Models)

IaaS (Infrastructure as a Service)

Servers, databases, storage, networks and VMs

(CSP is responsible for managing underlying hardware)

(Cloud Models)

PaaS (Platform as a Service)

building applications widget wadget wedgets

(building blocks like legos)

CSP takes care of all underlying platforms

(Cloud Models)

SaaS (Software as a Service)

application that we use that is hosted in someone elses infrastructure Salesforce, MS 365, Dropbox,

(Cloud Models)

XaaS (Anything as a Service)

any IT service that I use that I pay for can fall here

(Software (IT))

ERP (Enterprise Resource Planning)

integrates a lot of areas

(share analyze and report what is going on in the organization)

(Software (IT))

CRM (Customer Relationship Management)

Sales and Marketing and can track communications

(Software (IT))

Databases

backend of a software product.

structured - organized data into tables.

unstructured - "blob" data like video audio images could be emails

(Software (IT))

EDRMS (Electronic Document and Records Management System)

Like a file cabinet electronically

(access control provided)

found in legal and healthcare

(Software (IT))

CMS (content management system)

create and manage websites.

what you see is what you get website building.

(Software (IT))

Financial Systems

record financial data for organization.

features are general ledgers, accounts payable, accounts receivable, budgeting, forecasting, reporting

Change control is part of

Risk Management

Change Control Provides

Plan for changes - set aside time for changes

Downtime / maintenance windows schedules

Downtime / maintenance windows schedules are for

update/upgrade, patch, configuration

might be like once a month theres a maintenance window.

(Change Control)

Rollback plans

revert the changes that were made

(Change Control)

Validation Checks

final step in the change control process.

testing..

SOFTWARE Change Control

Deals with changing functionality or adding features.

The REQUESTOR is responsible for giving the "stamp of approval" for a software change.

- Requirements Definition: IDs the changes and IDs the expected Outcomes.

- Risk Assessment: IDs any issues that arise to address later and prepare if something happens.

MAKE CHANGES

Changes completed in a test / beta environment and perform validation checks

- Automated: scripts fast and efficient

- Manual: person runs series of tests and verifies the outcomes

CHANGE APPROVAL

- Once the test is complete the requestor gives the stamp of approval

CUSTOMER NOTIFICATION

- After approval of the requestor

RELEASE INTO PRODUCTION

- Release into production

CLOUD CHANGE CONTROL

CI/CD process allows us to make small changes often

Continuous Integration / Continuous Deployment (CI/CD) process

Process Groups/Phases (in order) or

Phases of Project Management Life Cycle

Concept or Discovery

Initiation

Planning

Execution

Closing

(Project Management Life Cycle)

Concept or Discovery (1)

feasibility study

business case

does it make sense

what are the benefits

(Project Management Life Cycle)

initiation (2)

officially starting the project

project charter

ID stake holders

gives project manager authority to use organization resources

(Project Management Life Cycle)

Planning (3)

what do we need to do

how are we going to do it

what resources do we need

how long is it going to take

what is it going to cost

(Project Management Life Cycle)

Execution (4)

when the team is executing the project management plan.

they're doing the work.

executing the work.

creating the deliverables.

as project manager we are leading and managing our team

(Project Management Life Cycle)

Closing (5)

close out project fully and professionally

lessons learned

what is the Agile Methodology

- iterative and incremental project management approach

- initially developed for IT software development projects but applicable for other projects

- focuses on customer value and team empowerment

- Customer receives output and provides feedback

- Project team makes improvements based on customer feedback

- Project manager role is more facilitator than task master

- Unique processes include SCRUM, Sprint, and daily standup meetings

what are PROJECT CONSTRAINTS

- factor that limits options for managing completing project requirements

- limitations / boundaries

- interrelated - changing in one constraint affects others

- balancing constraints

analyze impact on other constraints

balance stakeholder interests

balance accommodating any project changes

making tradeoff in favor of project goals

what are influences on projects and constraints

- change request

- scope creep

- constraint reprioritization

- interaction between constraints

- stakeholders / sponsors / management

- other projects

- organizational structure

(Risk Management Overview)

what are the Risk Management Steps (in order) (4 of them)

Identify the Risk

Analyze the Risk

Treat the Risk

Monitor the Risk

(Risk Response Strategies) (Negative Risks)

what are the Risk Response strategies for a negative risk

Avoid - eliminate the cause of the risk changing plan so that either risk will not occur or the risk will not affect the project

(Example - changing schedule, reducing scope, cancelling project)

Transfer - changing Plan by moving ownership to another party (example - insurance, subcontractor)

Mitigate - changing plan to reduce probability or impact or both (example - designing redundancy)

Accept - don't change plan, (passive acceptance - do nothing, Active acceptance - set up contingency)

(Negative Risk Response)

Avoid (1)

eliminate the cause of the risk changing plan so that either risk will not occur or the risk will not affect the project

(Example - changing schedule, reducing scope, cancelling project)

(Negative Risk Response)

Transfer (2)

changing Plan by moving ownership to another party

(example - insurance, subcontractor)

(Negative Risk Response)

Mitigate (3)

changing plan to reduce probability or impact or both

(example - designing redundancy)

(Negative Risk Response)

Accept (4)

don't change plan

(Passive acceptance - do nothing)

(Active acceptance - set up contingency)

(Risk Response Strategies) (Positive Risks)

what are the Risk Response strategies for a positive risk

Exploit - Remove the uncertainty take steps to make sure the opportunity is realized (you ensure that you will realize opportunity - you do everything to realize the opportunity) (Example - Buying off-the-shelf product (instead of developing) and delivering to customer to save time; using new technology to reduce cost of development; motivate team with rewards to meet the project deadline)

Share - Changing plan by sharing ownership with another party to make an attempt to avail the opportunity. (Example - Technology partnerships, launching new products jointly)

Enhance - changing plan to increase probability or impact or both (you try to realize the opportunity) (Example - adding more resources to reduce time, training people to improve quality)

Accept - Don't change plan (Passive acceptance - do nothing ; Active acceptance - set up contigency)

(Positive Risk Response)

Exploit (1)

Remove the uncertainty take steps to make sure the opportunity is realized (you ensure that you will realize opportunity - you do everything to realize the opportunity)

(Example - Buying off-the-shelf product (instead of developing) and delivering to customer to save time; using new technology to reduce cost of development; motivate team with rewards to meet the project deadline)

(Positive Risk Response)

Share (2)

Changing plan by sharing ownership with another party to make an attempt to avail the opportunity

(Example - Technology partnerships, launching new products jointly)

(Positive Risk Response)

Enhance (3)

changing plan to increase probability or impact or both (you try to realize the opportunity)

(Example - adding more resources to reduce time, training people to improve quality)

(Positive Risk Response)

Accept (4)

Don't change plan

(Passive acceptance - do nothing)

(Active acceptance - set up contingency)