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 Vikas Hazrati on Jan 06, 2010
Retroflection is a concept in which one substitutes self for environment, as in doing to self what one wants to do to someone else or doing for self what one wants someone else to do for self. Introspection is a form of retroflection that can be pathological or healthy. Based on a similar concept Yves Hanoulle started the Agile Retroflection of the day project.
According to Yves,
On my desk I have a set of cards from FranklinCovey. Every day I select a new card at random. Whatever the message on the card, I try to make this the motto of my day. This year, I want to create a similar experience for agilists around the world. That is why I created a Twitter Account for an agile Retroflection of the Day.
On this account Yves would post one message for people to think about in their teams, oragnization and life. On the basis of his question Yves hopes to find an Agilist each day who would blog an answer / opinion to the retroflection of the day.
Responding to the first retroflection message “If you could change 1 thing today what would it be?”, George Dinwiddie remarked that
That people could ask for, and could accept, the help they need and want.
According to George many teams, organizations do not ask for the help that they need because it might be an organizational culture to frown on people admitting that they don’t already know everything important. There could even be a lack of knowledge about the kind of help that they need which prevents them from asking for help. Apart from this many times they would not accept the help because of financial or other constraints.
Responding to another retroflection message about “ What is one thing you're ready /now/to change? Not the biggest thing, perhaps, but something meaningful.”, Simon Kirk responded that
I'm ready to change the way I communicate my ideas for the better; to slow myself down quickly, give myself room to hear other people more, talk less and hopefully from this help others change if they want to, too.
Follow the tweets for other interesting retroflection’s.
Agile Maturity Model Applied to Building and Releasing Software
SCM best practices for multiple processes, releases & distributed teams
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
I almost missed it.
The realize now that the name retroflection is a a bid confusing.
I'll write a post in a few weeks on why I have chosen it.
(I want to focus now on getting the answer rolling)
I have changed the concept a little bit since I have started.
Read the new rules/idea's here
paircoaching.wordpress.com/2010/01/05/agile-ret...
In Version 2.0 I have at least two opinions a day. As I like to promote women in agile, I give them the same bandwidth as men.
(If men don't like it, more people can write opinions)
I'm still looking for questions/reflections/retroflections and people that want to answer them; Please contact me on Twitter.com/YvesHanoulle or Twitter/Retroflection if you like the idea and want to help out.
y
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