Do not work for free: For bigger projects, sell requirements engineering or proof of concept.
---
---
#
# Write offerte
---
requirements are clear
schedule is realistic
risks are manageable
environment is controlled
ressources are appropriate
(financial) incentives match
---
# Making requirements
requirements:
function & non-function requirements
---
# Reasons for project failures
Unrealistic Goals, Schedules and Budgets
Failure to Address or Adequately Consider the Need to Simplify Complex Business Processes and Rules That Cannot Readily Be Implemented Into New Solutions
Governance and Oversight Lack Accountability and Responsibility
Organizational Culture and "Optimism Bias" During Supplier Evaluation and Procurement
Poor Project Discipline and Process Controls That Impede the Ability to Make Informed Decisions
Failure to Define, Control and Track Change Requirements, and, in Particular, to Reference Changes Back to the Original Need
Underestimation and Overconfidence With Regard to Risk
Insufficient Management or Technical Expertise From External Service Provider, System Integrator or Consultant
Failure to Understand or Address Nonfunctional and Technical Performance Requirements
Program Manager Not Provided With Adequate Authority to Ensure the Project Is Undertaken as Required
---
# Estimation
can't predict the future
class: center, middle
can estimate *relative* complexity
# Execute a successful project
concrete process:
- decompose tasks i
<i>No surprises.</i>
---
# basic tasks
ownership product -> outside
vision, expertise, schedule -> team
progress, relationships -> stakeholders
# Review progress & risks
Take corrective action early
---
# Making a schedule
# Manage expections
estimation:
complexity
You're 1# job!
milestones:
measurable
realistic
properly spaced
Communicate progress to stakeholders.
---
# During the project
# Manage changes
keep stakeholders informed
manage expectations
...
...
@@ -431,17 +380,14 @@ maintenance needs to be considered
