PMT-Manifest: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
| Zeile 15: | Zeile 15: | ||
** Risk mitigation is the driver for designing processes | ** Risk mitigation is the driver for designing processes | ||
** Do not invent theoretical risks to justify complex processes | ** Do not invent theoretical risks to justify complex processes | ||
[[File:p2_adjust.png]] | |||
* Constantly improve processes: | * Constantly improve processes: | ||
** Optimize processes to address risks with minimum amount of time, money and motivation | ** Optimize processes to address risks with minimum amount of time, money and motivation | ||
** If a process does not mitigate a severe risk, delete the process | ** If a process does not mitigate a severe risk, delete the process | ||
[[File:p3_no_detour.png]] | |||
* Do not misuse processes | * Do not misuse processes | ||
** A process shall ensure the product-quality of a work result. | ** A process shall ensure the product-quality of a work result. | ||
** Other goals like _improving team communication_, _hiding shortcomings of tools_, _spreading knowledge_, _ensuring execution of unrelated tasks_ shall be solved differently | ** Other goals like _improving team communication_, _hiding shortcomings of tools_, _spreading knowledge_, _ensuring execution of unrelated tasks_ shall be solved differently | ||
[[File:p4_overrule.png]] | |||
* Accountabilities must be clear: | * Accountabilities must be clear: | ||
** An accountable person can weight cost, schedule, team-motivation, product-quality, process-compliance and decide which one to drop. | ** An accountable person can weight cost, schedule, team-motivation, product-quality, process-compliance and decide which one to drop. | ||
** An accountable person has the authority to exchange team-members and to influence cost and schedule. | ** An accountable person has the authority to exchange team-members and to influence cost and schedule. | ||
[[File:p5_human_actor.png]] | |||
* Human decisions over Tools: | * Human decisions over Tools: | ||
** If a human wants to make a change, a tool may request a rationale and it may complain, but a tool may not stop her/him. | ** If a human wants to make a change, a tool may request a rationale and it may complain, but a tool may not stop her/him. | ||
** If this freedom is misused, remove people from the project. | ** If this freedom is misused, remove people from the project. | ||
[[File:p6_tool_actor.png]] | |||
* Tools don't change Human decisions: | * Tools don't change Human decisions: | ||
** If a tool wants to make a change, it must not overwrite data entered by humans. | ** If a tool wants to make a change, it must not overwrite data entered by humans. | ||
** A tool may have own status fields instead. | ** A tool may have own status fields instead. | ||
Aktuelle Version vom 1. Februar 2026, 10:12 Uhr
Andis PMT Manifest
Problem statement
- _No processes_ are fastest in execution but produce _random quality_
- _Too many processes_ are slow in execution and produce _suboptimal quality_
- A _motivated team_ that _anticipates a process_ produces higher quality than a demotivated team that simply follows a process
Solution
- Only a high risk justifies an expensive process
- Risk mitigation is the driver for designing processes
- Do not invent theoretical risks to justify complex processes
- Constantly improve processes:
- Optimize processes to address risks with minimum amount of time, money and motivation
- If a process does not mitigate a severe risk, delete the process
- Do not misuse processes
- A process shall ensure the product-quality of a work result.
- Other goals like _improving team communication_, _hiding shortcomings of tools_, _spreading knowledge_, _ensuring execution of unrelated tasks_ shall be solved differently
- Accountabilities must be clear:
- An accountable person can weight cost, schedule, team-motivation, product-quality, process-compliance and decide which one to drop.
- An accountable person has the authority to exchange team-members and to influence cost and schedule.
- Human decisions over Tools:
- If a human wants to make a change, a tool may request a rationale and it may complain, but a tool may not stop her/him.
- If this freedom is misused, remove people from the project.
- Tools don't change Human decisions:
- If a tool wants to make a change, it must not overwrite data entered by humans.
- A tool may have own status fields instead.