Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Chris Sims on Jul 16, 2008
An Agile Coach is someone who helps a team, or an entire organization, adopt and improve their agile practices. AgileCoachCamp, held this spring in Ann Arbor Michigan, was the first ever conference specifically for agile coaches. The participants, who came from as far away as India, Sweden, and Ukraine, self-organized to put on more than 60 sessions during the open space conference.
Some sessions focused on coaching skills such as listening and feedback. Others examined agile topics such as applying agile to a distributed team, or balancing process and engineering during an agile transition. There was even a session on using games to teach agile principles and practices.
In a session named "What Makes Agile Teams Succeed (or Fail)?" participants built a list of the key differentiators between the successful and unsuccessful teams that they had worked on. The result was a ranked list of those things that make the biggest difference. While the most important item, "Have motivated people" may be no surprise, the second item "Management by carefully chosen objectives and metrics" i s perhaps more interesting. An example shared was of a department manger who chose 'stories completed per week' as his primary metric. He felt that this measured actual progress, while having the beneficial side effect of encouraging smaller story size.
A session named "Transition Patterns" examined best practices for coaches when helping an organization transition to agile development. The group felt that teaching practices is an effective place to start, but that it is imperative that people come to understand the underlying principles if a transition is to fully succeed. It was strongly suggested that an agile transition team be formed to be the "eyes, ears, and muscles" of the transition. The idea was put forth that participants in the transition could be roughly grouped into 3 categories, and that each category would need a different type of coaching. The categories are:
Deborah Hartmann, who wrote this article on Powerful Questions, hosted a session on the topic. The group examined a variety of questions from the perspective of how powerful could they be and how likely would they be to open or close people to possibilities. The group quickly agreed that open-ended questions such as "What do you want to drink?" are more powerful than closed-ended questions such as "Do you want a cup of coffee?" Questions that begin with "Why..." were found to often have a blaming component, which can lead people to become defensive. Finally the group tried a coaching exercise in which a set of questions was the only tool used. Some of the questions included:
Participants in Agile Coach Camp did not have to pay a registration fee. Instead, each was required to write a position paper, answering the following questions:
A total of 74 position papers were submitted and can be found on the Agile Coach Camp wiki.
The conference was able to avoid handling money by matching sponsors directly with needs. Conference organizers Deborah Hartmann and Naresh Jain posted a list of things that needed to be paid for or provided, and sponsors signed up to provide these items. For example, Ron Jeffries and Chet Hendrickson covered the cost of the venue.
The conference wiki includes the posted session notes, as well as a photo gallery and the notes from the conference retrospective.
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
1 comment
Watch Thread Reply