From WikiVesalainen
| Line 15: | Line 15: | ||
* Focus more on Value than Costs | * Focus more on Value than Costs | ||
** Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software | ** Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software | ||
| − | ** Value | + | ** Value 3: Customer collaboration over contract negotiation |
| − | ** Value | + | ** Value 4: Responding to change over following a plan |
** Make sure you add value to the customer! | ** Make sure you add value to the customer! | ||
** If you are not producing value to the customer, you are focusing to the wrong topic and thus producing Waste! | ** If you are not producing value to the customer, you are focusing to the wrong topic and thus producing Waste! | ||
| Line 26: | Line 26: | ||
** I want to make clear separation with Scrum and Agile | ** I want to make clear separation with Scrum and Agile | ||
** If scrum (or other process definition) tells something, ask first will it make sense in Agile point of view | ** If scrum (or other process definition) tells something, ask first will it make sense in Agile point of view | ||
| + | |||
| + | * Focus more on reducing waste than improving efficiency | ||
| + | ** Principle 10: Simplicity–the art of maximizing the amount of work not done–is essential. | ||
| + | ** Value 3: Customer collaboration over contract negotiation | ||
| + | ** If you don't produce any waste, you cannot improve your efficiency | ||
| + | ** Measuring efficiency is impossible and thus measuring efficiency is waste | ||
| + | ** Measuring different kind of waste might be easier and may lead to better outcome | ||
== Information collection == | == Information collection == | ||
Revision as of 10:57, 8 July 2022
Contents
What is Migaler
It's Mika's Agile and Hacker way of producing Software
Agile
Agile is making decisions based on Agile Principles and Agile Values.
Agile Principles and Values
Agile manifesto defines 12 Agile principles and 4 values.
Waste
Waste is negative value. 9 typical types of waste.
My Focus
- Focus more on Value than Costs
- Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
- Value 3: Customer collaboration over contract negotiation
- Value 4: Responding to change over following a plan
- Make sure you add value to the customer!
- If you are not producing value to the customer, you are focusing to the wrong topic and thus producing Waste!
- Focus more on Agile than Scrum
- Value 1: Individuals and interactions over processes and tools
- Agile can be treated as an Adjective
- Scrum is more near to process definition, and thus is a noun
- I want to make clear separation with Scrum and Agile
- If scrum (or other process definition) tells something, ask first will it make sense in Agile point of view
- Focus more on reducing waste than improving efficiency
- Principle 10: Simplicity–the art of maximizing the amount of work not done–is essential.
- Value 3: Customer collaboration over contract negotiation
- If you don't produce any waste, you cannot improve your efficiency
- Measuring efficiency is impossible and thus measuring efficiency is waste
- Measuring different kind of waste might be easier and may lead to better outcome
Information collection
Agile links
- LinkedIn - Doing Agile Wrong
- Running Scrum (or Kanban) doesn't mean your Agile
- An iterative waterfall is not Agile
- Optimize feedback loops
- Agile planning principles
- Single Product -> Single Product Backlog
- Product vs Project
Agile videos
- Agile in 12 minutes
- Typical mistakes combined by Mikki from Allen Holub
- Agile vs. Agility (@30s Who is Allen Holub)
- Agile Architecture Part 1 (@114s What Agile is not)
- Agile Architecture Part 2
- NoEstimates (@998s Too large backlog)
- NoEstimates (@1082s Estimating is waste)
- The death of Agile (@976s Scrum vs Agile)
- War is Peace, Freedom is Slavery, Ignorance is Strength, Scrum is Agile (@100s Jira)