留学生考试辅导 SWEN90016 Software Processes and Project Management - 2 - IT ALL STARTS

School of Computing and Information Systems The University of Melbourne
Copyright University of Melbourne 2017-2022
2022 – Semester 1 Week 1

Software Processes & Project Management

Week 1 – Intended Learning Objectives
Module 3: Projects
2. Explore the key drivers of why projects fail / succeed.
3. Understandhoworganisationsselectthebest/rightprojects (Project Screening).
4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them.
5. Explore various investment techniques and financial models.
6. Understand what a Project Charter is and how it is used.
An initial look at (some) Project Management Methodologies /
Standards.
SWEN90016 Software Processes and Project Management – 2 – IT ALL STARTS HERE

Module 3.1 – PM Methodologies / Standards
SWEN90016 Software Processes and Project Management – 3 – IT ALL STARTS HERE

Module 3.1 – Key Elements of Project Management Methodologies / Standards
• Traditional approach used for over 40 years
• Requirements must be defined at the start
• Little / no alternations
• Sequential – Complete 1 task and then the next
• Used in large scale SW development where thorough planning and predictability
is required
• Extensive planning, this thoroughness often results in more accurate timelines and budgets
• Difficult to apply changes or modify / correct previous steps (water can’t run backwards), need to be proactive in anticipating problems
SWEN90016 Software Processes and Project Management – 4 – IT ALL STARTS HERE

Module 3.1 – Key Elements of Project Management Methodologies / Standards
• Focuses on adapting to changing situations
• Reliant on constant and regular feedback
• Focuses on iterative outcomes delivering value as quickly as possible & collaboratively
• Small manageable actions and activities
• Involvement & ownership across the team – Team members self select work
• Customer focus over formalised sign-offs
• Retains flexibility while continually producing outcomes – less rework
• Greater communication & engagement – increased buy in across the team of the end
• Difficult to do without experience – especially an experienced Scrum Master
• Large projects co-location a problem
• Difficult to contract suppliers
SWEN90016 Software Processes and Project Management – 5 – IT ALL STARTS HERE

Module 3.1 – Key Elements of Project Management Methodologies / Standards
Structured Project Management Methodologies e.g. PRINCE 2 etc
• Widely used and accepted – Consulting, Private and Government
• Process orientated approach
• Divides projects into multiple stages
• Detailed and thorough
• Must have a clear need, a target customer, realistic benefits, and a thorough cost analysis
• Extensive documentation is helpful with corporate planning & tracking
• Difficult and untimely to adapt changes and apply these to all documentation
SWEN90016 Software Processes and Project Management – 6 – IT ALL STARTS HERE

Module 3.1 – Project Methodologies – Which on is the right one?
• They all have a place and all can be appropriate
• It is like selecting the best recipe – it all depends on your ingredients
• Items (ingredients) to consider include:
– Clarity and stability of scope
– Timelines
– Tools to support / drive the process
– People / knowledge
– Organisational maturity
– Stakeholder buy-in
– Experience in the various approaches
SWEN90016 Software Processes and Project Management – 7 – IT ALL STARTS HERE

Week 1 – Intended Learning Objectives
Module 3: Projects
1. An initial look at (some) Project Management Methodologies / Standards.
2. Explore the key drivers of why projects fail / succeed.
3. Understandhoworganisationsselectthebest/rightprojects
(Project Screening).
4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them.
5. Explore various investment techniques and financial models.
6. Understand what a Project Charter is and how it is used.
SWEN90016 Software Processes and Project Management – 8 – IT ALL STARTS HERE

Module 3.2 – Project Success / Failure – You decide
Original estimate
• 12 months
Final outcomes
• $2m (60% increase)
• 18 months (50% longer)
SWEN90016 Software Processes and Project Management -9- IT ALL STARTS HERE

Redefined the market in Tracking, Pricing, Staff Pay, Customer Flexibility and Transparency
Original estimate
• 12 months
Final outcomes
• $2m (60% increase)
• 18 months (50% longer)
SWEN90016 Software Processes and Project Management -10- IT ALL STARTS HERE

Module 3.2 – Project Success / Failure – You decide
Failure or Success?
• Original estimate – $5 million
• Final outcomes – $1.52 billion
SWEN90016 Software Processes and Project Management -11- IT ALL STARTS HERE

Module 3.2 – Project Success / Failure – You decide
Failure or Success?
• Original estimate – $500million
• Final outcomes
– $1.5billion – >5 years
SWEN90016 Software Processes and Project Management -12- IT ALL STARTS HERE

Module 3.2 – Project Success / Failure – You decide
Failure or Success?
• Original estimate – $7m
• Final outcomes
– $102m (1,357% more)
– 16 years (10 years longer)
SWEN90016 Software Processes and Project Management -13- IT ALL STARTS HERE

Module 3.2 – Software Projects
History tells us we have failed.
ALL IT PROJECTS
Successful
29% 27% 31% 28% 29%
Challenged
22% 17% 19% 17% 19%
• Successful: project is completed on-time and on-budget, with all features and functions as initially specified.
• Failed: project is cancelled at some point during the development cycle. Chaos Reports: Source: 2015 Chaos Report www.projectsmart.co.uk/white-papers/chaos-report.pdf
• Challenged: completed and operational but over-budget, over the time estimate or offers fewer features and functions than planned.
SWEN90016 Software Processes and Project Management – 15 – IT ALL STARTS HERE

Module 3.2 – Software Projects – What determines success?
Success Factors %
1. Executive Sponsorship 15%
2. Emotional Maturity 15%
3. User Involvement 15%
4. Optimisation – Statement of Requirements 15%
5. Skilled Resources 10%
6. Standard Architecture 8%
7. Agile Process 7%
9. Project Management Expertise 5%
10. Clear Business Objectives 4%
Chaos Reports: www.projectsmart.co.uk/white-papers/chaos-report.pdf www.infoq.com/articles/standish-chaos-2015
• Factors have remained relatively constant
• If we know the reasons why can’t we fix / improve it?
• 60% (first 4) are non technical items and difficult to change
• Broader organisational context and system at play
SWEN90016 Software Processes and Project Management – 16 – IT ALL STARTS HERE

Module 3.2 – Digital transformation projects – some stories about why projects failed
• GE created a new digital business unit but was focused on size instead of quality
• Ford started a new digital service that was separate from the rest of the company instead of integrating digital solutions
• Procter & Gamble didn’t consider the competition or impending economic crash
Forbes: Companies That Failed At Digital Transformation And What We Can Learn From Them https://www.forbes.com/sites/blakemorgan/2019/09/30/companies-that-failed-at-digital-transformation- and-what-we-can-learn-from-them/?sh=7bfac7ec603c. Accessed 29 July 2021
SWEN90016 Software Processes and Project Management – 17 – IT ALL STARTS HERE

https://www.forbes.com/sites/stevedenning/2021/05/23/why-digital-transformations-are- failing/?sh=319ac8437617 Accessed 29 July 2021
SWEN90016 Software Processes and Project Management – 18 – IT ALL STARTS HERE

Week 1 – Intended Learning Objectives
Module 3: Projects
1. An initial look at (some) Project Management Methodologies / Standards.
2. Explore the key drivers of why projects fail / succeed.
4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them.
5. Explore various investment techniques and financial models.
6. Understand what a Project Charter is and how it is used.
Understand how organisations select the best / right projects
(Project Screening).
SWEN90016 Software Processes and Project Management – 19 – IT ALL STARTS HERE

Module 3.3 – Project Screening and where to start
“If you don’t know where your going any road will take you there”. Any Road by – The Beatles
• The place to start is at the beginning!
• Organisations need a formal, structured approach to:
• Prioritise;
• Have oversight; and
• Drive accountability across all projects.
SWEN90016 Software Processes and Project Management – 20 – IT ALL STARTS HERE

Module 3.3 – Project Screening and where to start
Transformational Regulatory
SWEN90016 Software Processes and Project Management – 21 – IT ALL STARTS HERE

Week 1 – Intended Learning Objectives
Module 3: Projects
1. An initial look at (some) Project Management Methodologies / Standards.
2. Explore the key drivers of why projects fail / succeed.
3. Understandhoworganisationsselectthebest/rightprojects (Project Screening).
5. Explore various investment techniques and financial models.
6. Understand what a Project Charter is and how it is used.
Understand the Project Initialization process, Business Case
structure and why organisations use them.
SWEN90016 Software Processes and Project Management – 22 – IT ALL STARTS HERE

Module 3.4 – Project Initialization
There are many approaches and methodologies that are widely used across industry with organisations favoring standard industry ones (PRINCE2, PMBOK, Agile etc) or usually a modified version of these they make their own.
They all have Pro’s & Con’s.
Prince2 AGILE
Software PM Activities

Back2Basics: Software Project Management: Activities and Roles

SWEN90016 Software Processes and Project Management – 23 – IT ALL STARTS HERE

Module 3.4 – Setting up a project for success. A Business Case is the key.
The purpose of the Business Case is to establish mechanisms to judge whether the project is (and remains) desirable, viable and achievable as a means to support decision making in its initial and continued investment.
• Providesafactualbaseforkeydecisionsmakerstodecideifthe project should be undertaken
• Demonstrateshowtheprojectaddsvaluetotheorganisation
• Hasasetofpre-definedstandardorganisationalcharacteristics (costs, benefits, risk, etc.)
• It is not all about size – size depends on the cost / benefit
• It is a living document throughout the project that should be reviewed and signed off at key stages
SWEN90016 Software Processes and Project Management – 24 – IT ALL STARTS HERE

Module 3.4 – Setting up a project for success. The Business case is key
Business case contains:
• Executive summary
• Reasons / explanation of why it is required • Business options
• Expected benefits
• Expected dis-benefits
• Timescale
• Investment appraisal
• Major risks
Source: www.prince2.com
SWEN90016 Software Processes and Project Management – 25 – IT ALL STARTS HERE

Module 3.4 – Business Case. Who is responsible for what?
Responsibilities
1. Provides Mandate / The go ahead.
2. Holds Senior Users accountable for benefits realisation.
3. Responsible for conducting post projects benefits validation.
Executive / Sponsor
1. Owns the Business Case.
2. Responsible for reviewing the benefits throughout the project.
Senior Users
1. Responsible for accepting the benefits and delivering them.
2. Responsible for ensuring the delivered products are to the appropriate quality
3. Provides on-going actual V forecasted benefit realisation.
Project Manager
1. Prepares the Business Case.
2. Conducts Risk assessment and impact analysis.
3. Assess and updates the Business Case at each defined stage.
Project Assurance / QA
1. Assists in developing the Business Case.
2. Ensure value for money and risks are continuously managed.
3. Monitors change to the Business Case and validates it.
Project Support
1. Responsible for capturing data and preparing management reports.
2. Key support point for all project stakeholders – schedules, cost analysis,
minutes, actions, supplier liaison etc.
SWEN90016 Software Processes and Project Management – 26 – IT ALL STARTS HERE

Week 1 – Intended Learning Objectives
Module 3: Projects
1. An initial look at (some) Project Management Methodologies / Standards.
2. Explore the key drivers of why projects fail / succeed.
3. Understandhoworganisationsselectthebest/rightprojects (Project Screening).
4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them.
5. Explore various investment techniques and financial models.
6. Understand what a Project Charter is and how it is used.
SWEN90016 Software Processes and Project Management – 27 – IT ALL STARTS HERE

Module 3.5 – It is all about the money!
• For non mandatory projects, the primary benefit is financial
• Multiple investment techniques are used to analyse the investment required / financial benefit
• Some (there are many more) techniques include:
• Return On Investment
• Net Present Value
• Payback period
• Rough Order of Magnitude
• However, it is not always about the best return – organisations need to invest in all parts of their business
SWEN90016 Software Processes and Project Management – 28 – IT ALL STARTS HERE

Module 3.5 – Investment Techniques – Return On Investment (ROI)
• ROI is income divided by investment
• ROI = (total discounted benefits – total discounted costs) / total discounted costs
• The higher the ROI % or higher the ratio of benefits to costs, the better it is
• Many organisations have a required rate of return or minimum acceptable rate of return on investment for projects (11% to 14%)
SWEN90016 Software Processes and Project Management – 29 – IT ALL STARTS HERE

Module 3.5 – Investment Techniques – Net Present Value (NPV)
• NPV is one of the most often used quantitative/financial models for project selection
• NPV is a method of calculating the expected net monetary gain or loss from an investment (project) by discounting all future costs and benefits to the present time
• Projects with a positive NPV should be considered if financial value is a key criterion
• Generally, the higher the NPV, the more favourable a project is
SWEN90016 Software Processes and Project Management – 30 – IT ALL STARTS HERE

Module 3.5 – Investment Techniques – Payback period
• The payback period is the amount of time it takes a project before the accrued benefits surpass accrued costs or how much time an investment takes to recover its initial cost
• Based on tracking the net cash flow across each year to determine the year that net benefits overtake net costs (not discounted cash flows)
• Many organizations want IT projects to have a fairly short payback period (< 1 year) due to the changing nature of technology SWEN90016 Software Processes and Project Management - 31 - IT ALL STARTS HERE Module 3.5 – Investment Techniques – Project Estimation Rough Order of Magnitude (ROM) The Cone of Uncertainty for cost estimates Limited accuracy: • ROM: -25% ... +75% • Budget: -10% ... +25% Reference: , Information Technology Project Management, pg 280 SWEN90016 Software Processes and Project Management -32- IT ALL STARTS HERE Margin for Error Week 1 – Intended Learning Objectives Module 3: Projects 1. An initial look at (some) Project Management Methodologies / Standards. 2. Explore the key drivers of why projects fail / succeed. 3. Understandhoworganisationsselectthebest/rightprojects (Project Screening). 4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them. 5. Explore various investment techniques and financial models. 6. Understand what a Project Charter is and how it is used. SWEN90016 Software Processes and Project Management - 33 - IT ALL STARTS HERE Module 3.6 – It all begins with a Project Charter http://blog.zilicus.com/software-project-management-activities-roles/ SWEN90016 Software Processes and Project Management -34- IT ALL STARTS HERE Week 1 - Simple Project Charter Know your project’s risks Target Date: [Date] Write out the project description here. Write out the project description here. Write out the project description here. Write out the project description here. Write out the project description here. Write out the project description here. Write out the project description here. Person 1 – Project Manager Person 2 – Team Lead Person 3 – Analyst Person 4 – Developer Person 5 – Quality Person 6 – Trainer Person 7 – Other Person 8 – Other Person 9 – Other Person 10 – Other Milestone 1 [Date] [Description of what will be accomplished on this milestone] Milestone 2 [Date] [Description of what will be accomplished on this milestone] Milestone 3 [Date] [Description of what will be accomplished on this milestone] Cost Savings Time Savings Revenue Gain SWEN90016 Software Processes and Project Management -35- IT ALL STARTS HERE Week 1 – Intended Learning Objectives Module 3: Projects 1. An initial look at (some) Project Management Methodologies / Standards. 2. Explore the key drivers of why projects fail / succeed. 3. Understandhoworganisationsselectthebest/rightprojects (Project Screening). 4. UnderstandtheProjectInitializationprocess,BusinessCase structure and why organisations use them. 5. Explore various investment techniques and financial models. 6. Understand what a Project Charter is and how it is used. SWEN90016 Software Processes and Project Management - 36 - IT ALL STARTS HERE 程序代写 CS代考加微信: powcoder QQ: 1823890830 Email: powcoder@163.com

Related Posts