Saturday, April 2, 2011

Agile Principle 8: Sustainable Pace

Let's take a look at the eighth underlying principle of the agile manifesto:
"Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.
  • "Agile processes promote sustainable development" - This is not a principle but rather a presumption which has to be proven by applying agile practices. In my point of view this sentence should be removed from the eighth underlying principle or at least be rephrased.
  • "The sponsors, developers, and users" - It's again a cross-functional approach which includes the whole team and all people involved in the product creation chain.
    Values: Communication
    Principles: Collaboration and cooperation between all stakeholders, Diversity
    Practices: Real Customer Involvement, Whole Team
  • "should be able to maintain a constant pace" - The people involved in the product creation chain must neither suffer from excessive labor nor sit around idling and waiting. An important practice especially for the team is collective ownership of both code and responsibility. Let's call it shared commitment.
    Values: Commitment, Focus, Courage
    Principles: Frequent Delivery, Flow, Baby Steps
    Practices: Energized Work (Continuous Pace)
  • "indefinitely" - It's not enough to keep a constant pace at the start of the project or for just a few iterations. Especially at the end of a project all people should keep calm and just "flow" with that constant pace.
    Values: Commitment
    Principles: Humanity, Flow, Limit Work in Progress
    Practices: Motivation, Energized Work (Continuous Pace)
To say it in two words, the eighth principle is about "Sustainable Pace".


Also read in this blog post series:
Posted by at 1 comment:
Labels:

Wednesday, March 30, 2011

Agile Principle 7: Working Software

Let's take a look at the seventh underlying principle of the agile manifesto:
"Working software is the primary measure of progress."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.

  • "Working software" - it does not matter how many modules, interfaces, and documents we have in progress. The only thing that counts is completed, fully functional pieces of the wanted product.
    Values: Commitment, Focus
    Principles: Quality, Active User Involvement, Build Integrity In
    Practices: Definition of Done, Acceptance Tests, Real Customer Involvement, Customer Tests, Product Demonstration
  • "is the primary measure of progress" - no one is interested in the number of work hours, lines of code, or any other technical metric. Only done and releasable features are important.
    Values: Simplicity, Commitment, Feedback
    Principles: Business Value, Frequent Delivery,
    Practices: Incremental Deployment, Small Releases, Release Burndown, Product Demonstration, Measurements
Posted by at No comments:
Labels:

Thursday, March 24, 2011

Agile Principle 6: Face-to-Face Conversation

Let's take a look at the sixth underlying principle of the agile manifesto:
"The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.
  • "The most efficient and effective method of conveying information" - it is not enough to make information available in a passive way but it should be pushed actively to the target audience.
    Values: Communication, Openness
    Principles: Transparency, Make Work Visible, Tell don't ask
    Practices: Osmotic Communication, Informative Workspace
  • "to and within a development team" - do not only expect active communication from the outside of your team but also foster active communication with your own team members.
    Values: Communication, Openness
    Principles: Humanity, Transparency, Make Work Visible, Tell don't ask
    Practices: Osmotic Communication, Informative Workspace, Servant Leadership
  • "is face-to-face conversation" - do not open inefficient communication channels like writing things down on paper, emails, and bug-tracking systems. Rather talk to the receiver of your message directly via phone, video, or in the best case in front of a white board from person to person.
    Values: Focus, Feedback
    Principles: Tell don't ask, Mutual Benefit, Collaboration and cooperation between all stakeholders
    Practices: Sit Together, Team Room
To say it in four words, the sixth principle is about Face-to-Face Conversation.



Also read in this blog post series:
Posted by at 1 comment:
Labels:

Monday, March 21, 2011

Agile Principle 5: Support and Trust

Let's take a look at the fifth underlying principle of the agile manifesto:
"Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.
  • "Build projects around motivated individuals" - search and hire Drive-Driven Personalities who love their job and are passionate about what they're doing. Get rid of unskilled or even destructive people as they will have a major negative impact on the project's success.
    Values: Commitment, Courage
    Principles: Opportunity, Amplify Learning, Humanity, Accepted Responsibility
    Practices: Motivation, Energized Work (Continuous Pace)
  • "Give them" - as the Holy Bible already mentions "give, and it will be given to you". Do not demand results from the team but give them what they demand for their private and professional life.
    Values: Respect
    Principles: Empower the Team, Humanity, Supportive Culture
    Practices: Servant Leadership
  • "the environment" - the team needs a proper workspace and the best equipment available to do its work in a professional manner. This is also about the team's processes from a larger organizational point of view. Surround the team with lean structures, try to avoid beaurocratic structures impeding the team's performance and pace.
    Values: Simplicity, Openness
    Principles: Empower the Team, Supportive Culture
    Practices: Whole Team, Team Room
  • "and support they need" - help the team instantly as they get stuck. Clear their path and remove any obstacles. Show them alternative ways to go.
    Values: Courage, Focus
    Principles: Improvement, Adaption, Supportive Culture
    Practices: Servant Leadership
  • "trust them to get the job done" - if you have motivated individuals on the team, you also have to trust them. They are the people knowing exactly how to do their job. Do not let anyone else decide and plan how the team should work and who is going to do what and when.
    Values: Respect, Courage
    Principles: Self-organizing Team, Empower the Team, Humanity, Diversity, Supportive Culture
    Practices: Whole Team, Team Room, Team Continuity, Personal Safety, Energized Work (Continuous Pace)
To say it in three words, the fifth principle is about Support and Trust.




Also read in this blog post series:
Posted by at 1 comment:
Labels:

Thursday, March 17, 2011

Agile Principle 4: Cross-Functional Collaboration

Let's take a look at the fourth underlying principle of the agile manifesto:
"Business people and developers must work together daily throughout the project."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.
  • "Business people" - there are people with a vast knowledge of the product's target markets, its users and customers, and its needed features. These people should not be the developers of the product as they normally tend to implement developer-centric, fancy things. The 'business people' should be the ones grooming and prioritizing the product features of the largest customer and business value.
    Values: Respect, Communication
    Principles: Active user involvement, Economics
    Practices: Real customer Involvement, Whole Team
  • "Developers" - in terms of "product developers" not solely coding software developers. This includes also testers, technical writers, interface designers, business analysts, and whatever role is necessary to give input and create a working software product.
    Values: Respect, Communication
    Principles: Diversity, Humanity
    Practices: Whole Team
  • "must work together" - it is not helpful to let experts work on their own and pass over their finished results to the next expert in a process chain. Their output rather should be the result of strong collaboration and communication.
    Values: Communication
    Principles: Diversity, Mutual Benefit, Collaboration and cooperation between all stakeholders
    Practices: Whole Team
  • "daily" - collaboration and communication do only work well on a continuous basis. The Product Owner has to be present and available to the team during the whole iterations, not just at the planning and review meeting.
    Values: Focus, Commitment
    Principles: Flow, Iterative
    Practices: Sit Together, Osmotic Communication, Daily Scrum, Whole Team
  • "throughout the project" - collaboration and communication do not happen during specific project 'phases' only. They need to happen right from the start until the end of the project.
    Values: Commitment, Focus
    Principles: Frequent Delivery, Flow, Iterative, Collaboration and cooperation between all stakeholders
    Practices: Team Continuity, Energized Work (Continuous Pace)
To say it in three words, the fourth principle is about Cross-Functional Collaboration.



Also read in this blog post series:
Posted by at No comments:
Labels:

Tuesday, March 15, 2011

Book: Lyssa Adkins - Coaching Agile Teams


The definitive must-read for every Scrum Master, agile manager, and agile coach!

Author: Lyssa Adkins

Rating: highest recommendation!

This is one of the most valuable books I've ever read in my agile life. More than 300 pages full of practical advice with many examples make this book a perfect reference on the desk of every Scrum Master, agile manager, and agile coach.

Lyssa has a very nice and easy to read style of writing and yet offers so many insights. Following topics are covered in her book:
  • You and your mastery as a coach
  • Coach as Coach-Mentor
  • Coach as Facilitator
  • Coach as Teacher
  • Coach as Problem Solver
  • Coach as Conflict Navigator
  • Coach as Collaboration Conductor
  • Agile Coach Failure, Recovery, and Success Modes
  • Your Journey as Agile Coach
There's nothing more to say about this book other than: buy it, study it, and live it!

It may sound pathetic but this book deeply changed the way I think about and practice agile methods. It probably even changed my life.

Thanks, Lyssa, for writing this book!


Posted by at 1 comment:
Labels:

Agile Principle 3: Frequent Delivery

Let's take a look at the third underlying principle of the agile manifesto:
"Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale."
What does that really mean? What are the implications for our daily business? Let's analyze this principle and see where this gets us.
  • "Deliver" - actually have something finished that is worth being given to the users.
    Values: Courage, Commitment
    Principles: Deliver as fast as possible
    Practices: Incremental Deployment, Small Releases, Sprint Review, Product Demonstration
  • "working software" - the results of our efforts must not be theoretical concepts or prototypes, but a functional software product the user is able to work with effectively
    Values: Focus, Commitment
    Principles: Quality
    Practices: Definition of Done, Acceptance Tests, Sprint Review, Product Demonstration
  • "frequently" - give an usable product more often to the users than just once at the end of the development project
    Values: Focus, Courage
    Principles: Frequent Delivery
    Practices: Incremental Deployment, Small Releases
  • "from a couple of weeks to a couple of months" - keep the iterations short so they are easily manageable and clearly arranged
    Values: Focus
    Principles: Deliver as fast as possible, Iterative
    Practices: Iteration
  • "with a preference to the shorter timescale" - create results early and often so the customer is able to react and decide quickly
    Values: Focus, Simplicity
    Principles: Iterative, Limit Work in Progress, Deliver as fast as possible, Eliminate Waste
    Practices: Incremental Deployment, Small Releases, Sprint Backlog, Iteration
There's not much to summarize here but to say it in two words, the third principle is about Frequent Delivery.



Also read in this blog post series:
Posted by at No comments:
Labels:
Subscribe to: Posts (Atom)