-posted as test, from LinkedIn
Agile has been around for over 2 decades now. Most every method talks about values, principles and practices. The Agile Manifesto, for example, is comprised of 4 values and 12 principles. XP, Scrum, Kanban, SAFe, LeSS and Nexus have added a considerable number of principles and practices as well. However, there has been little discussion of the laws of software development and insufficient discussion of the objectives of the practices of its popular frameworks, methods, etc. This blog series discusses both the laws of software development and provides a more detailed explanation of the objectives of the key practices of several popular frameworks and methods.
Let’s first define what is meant by these terms:
Value (noun) – a person’s principles or standards of behavior; one’s judgment of what is important in life.
Principles - a fundamental truth or proposition that serves as the foundation for a system of belief or behavior or for a chain of reasoning.
Practice (noun) – the actual application or use of an idea, belief, or method as opposed to theories about such application or use.
Law – a statement of fact, deduced from observation, to the effect that a particular natural or scientific phenomenon always occurs if certain conditions are present
Objective (noun)– a thing aimed at or sought, a goal. In our context these will be the objectives of practices.
Now, let’s go through and give an example of each:
Value (noun) – From the Agile Manifesto: We value individuals and interactions …
Principles – From the Agile Manifesto: Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage
Practice (noun) – From Scrum and XP – use time-boxed iterations from 1 week to 30 days
Law – From Lean – working on too many things will introduce additional work into the process
Objective (noun) – One objective of time-boxing is to get quicker feedback.
This is just the beginning of this blog series. I hope to present a law or objective every other day or so to elaborate on why these are so important and to provide examples of many laws and objectives that are not well known, but should be. My next one will talk about "Scrum-but" and why much of Kanban these days is neither Scrum nor Kanban.