Quantification Evaluation Steps (1/6)
Give this one a try later!
Step 1: Understand the client's business environment
Risks
Give this one a try later!
➢ Risk Register: list of all identified risks for monitoring
➢ Risk Management
o Risk Assessment: process of identifying assets, threats, and vulnerabilities
o Risk Analysis: process of valuating the potential risks
▪ Cost Benefit Analysis
o Risk Response: determining how to react to the risks so that we can
continue with business
➢ Secondary Risk: a new risk that is introduced as a result of a risk
, response
➢ Residual Risk: the risk amount left over after a risk response
➢ Total Risk: the amount of risk before any risk response is implemented
o Usually calculated as: Threats vulnerability asset value
Quantification Evaluation Steps (4/6)
Give this one a try later!
Step 4: Receive Approval; Then Design, Develop, Implement (and Test!)
the TO-BE process
Project Management Methodology
Give this one a try later!
➢ Methodology: a formalized approach to implementing a process or
framework
o Derived from various sources ➢ Choosing a methodology can be based
on your
o Project
o Organization o Client
o Preference
o Previous Experience
➢ Waterfall & Agile
Quantification Results
Give this one a try later!
, ➢ Analyze the data
➢ Does the TO-BE process result in one or more of the following?:
o Improved Revenue
o Reduced Expenses
▪ Including cost of the new process
o Improved Net Income
➢ Did you solve the problem? How does it compare to the estimate?
Calculate actual ROI
➢ Showing the differences between the AS-IS and TO-BE processes with
quantification (time and or money (both is better)) will allow executive
management to make an informed decision
➢ Quantification can make or break your project proposal
Proposed Technical Solutions
Give this one a try later!
➢ In this class, we don't just worry about the process. We are here to apply
technology solutions to business processes
➢ Usually, we want to present three potential technical solutions that can
be implemented in the TO-BE process, to improve the AS-IS process
➢ The requirements gathered at the beginning are needed to produce an
"Acceptance Criteria" for your client/customer/organization
o Acceptance Criteria are those requirements that need to be met for the
new solution to be accepted/implemented
▪ Can be a combination of requirements
o This is usually done in teams and interacting with the product owner and
executives o Of course, this is an iterative process to better understand
what is necessary and wanted
Build or Buy Decision
Give this one a try later!
, o Would you build:
▪ Accounting Software? Payroll Software? Timecard Software? Inventory
Tracking Software? CRM? Job Tracking?
o Things to consider:
▪ How much will the software be used
▪ When will the software be needed to be used
▪ How will the business / market change over time?
▪ Does the business expect to grow or shrink
▪ Do you have a dedicated team to support the software?
▪ Are needs vs wants considered?
Project Management Areas
Give this one a try later!
1. Scope
2. Schedule
3. Cost
4. Quality
5. Risk
6. Communications
7. Human Resources
8. Procurement
9. Stakeholder
- The Project Manager plays the role of Integrator for these 9 areas
Quantification Evaluation Steps (2/6)
Give this one a try later!
Step 2: Determine and Quantify the AS-IS (current) process
Give this one a try later!
Step 1: Understand the client's business environment
Risks
Give this one a try later!
➢ Risk Register: list of all identified risks for monitoring
➢ Risk Management
o Risk Assessment: process of identifying assets, threats, and vulnerabilities
o Risk Analysis: process of valuating the potential risks
▪ Cost Benefit Analysis
o Risk Response: determining how to react to the risks so that we can
continue with business
➢ Secondary Risk: a new risk that is introduced as a result of a risk
, response
➢ Residual Risk: the risk amount left over after a risk response
➢ Total Risk: the amount of risk before any risk response is implemented
o Usually calculated as: Threats vulnerability asset value
Quantification Evaluation Steps (4/6)
Give this one a try later!
Step 4: Receive Approval; Then Design, Develop, Implement (and Test!)
the TO-BE process
Project Management Methodology
Give this one a try later!
➢ Methodology: a formalized approach to implementing a process or
framework
o Derived from various sources ➢ Choosing a methodology can be based
on your
o Project
o Organization o Client
o Preference
o Previous Experience
➢ Waterfall & Agile
Quantification Results
Give this one a try later!
, ➢ Analyze the data
➢ Does the TO-BE process result in one or more of the following?:
o Improved Revenue
o Reduced Expenses
▪ Including cost of the new process
o Improved Net Income
➢ Did you solve the problem? How does it compare to the estimate?
Calculate actual ROI
➢ Showing the differences between the AS-IS and TO-BE processes with
quantification (time and or money (both is better)) will allow executive
management to make an informed decision
➢ Quantification can make or break your project proposal
Proposed Technical Solutions
Give this one a try later!
➢ In this class, we don't just worry about the process. We are here to apply
technology solutions to business processes
➢ Usually, we want to present three potential technical solutions that can
be implemented in the TO-BE process, to improve the AS-IS process
➢ The requirements gathered at the beginning are needed to produce an
"Acceptance Criteria" for your client/customer/organization
o Acceptance Criteria are those requirements that need to be met for the
new solution to be accepted/implemented
▪ Can be a combination of requirements
o This is usually done in teams and interacting with the product owner and
executives o Of course, this is an iterative process to better understand
what is necessary and wanted
Build or Buy Decision
Give this one a try later!
, o Would you build:
▪ Accounting Software? Payroll Software? Timecard Software? Inventory
Tracking Software? CRM? Job Tracking?
o Things to consider:
▪ How much will the software be used
▪ When will the software be needed to be used
▪ How will the business / market change over time?
▪ Does the business expect to grow or shrink
▪ Do you have a dedicated team to support the software?
▪ Are needs vs wants considered?
Project Management Areas
Give this one a try later!
1. Scope
2. Schedule
3. Cost
4. Quality
5. Risk
6. Communications
7. Human Resources
8. Procurement
9. Stakeholder
- The Project Manager plays the role of Integrator for these 9 areas
Quantification Evaluation Steps (2/6)
Give this one a try later!
Step 2: Determine and Quantify the AS-IS (current) process
