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 Apr 11, 2008
Is all this leading to overburdening of facilitators? Are they trying to do much more than they can possibly handle?
- Basic Agile Work administrative skills.
- Obstacle removal.
- Team dynamics and development.
- Coaching individuals.
- Organizational development.
- Training groups and teams.
- Promoting agile methods.
- Strategic application of agile methods.
I have learned I need to limit the number of days in a week that I facilitate, especially if there is conflict in the group. I've learned that if I book more than three full days a week, I'm past what my heart and energy want to do.Another strategy was suggested by Jo Nelson
I spent as much time as I could carve out alone, where I didn't have to interact with anyone. For me, the natural world is re-energizing, so I found places and times I could go for long, slow, wondering walks alone. I read upbeat fiction, and did creative hand craft work that demanded no intellectual or verbal energy. I did lots of yoga and breathing exercises. I listened to the music that centres me.John Powderly seems to have come out with an interesting way to deal with facilitation burnout, he added:
I no longer call myself a facilitator! Facilitation is now a skill and/or a philosophical basis for what I do, and less associated with my identity. Currently, I call myself "a strategic research, planning andGroup members seemed to agree that, with all the primary and secondary tasks associated with facilitation, burnout was a reality. The difference lies in identifying when you are close to that stage and then taking corrective action immediately. Jo's closing remarks suggest that the key is in noticing when the facilitator is getting close to burnout. This is the time to reflect on your core values, and try to evolve a strategy which keeps you energized and sane. The final step is to follow those strategies.
collaboration specialist", but this may still change as I continue to emerge.
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
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!
It sounds a bit like being an entrepreneur or a real estate agent. Your customers and clients need you almost around the clock, and if you want to be great, you have to almost be "on" nearly all the time. Of course, entrepreneurs and real estate agents are paid on commission, so there's an incentive there that would be lacking in a facilitator.
Your customers and clients need you almost around the clock, and if you want to be great, you have to almost be "on" nearly all the time.
I think that is the key and in order to be there for the client and the team the facilitators tend to overwork and take on more work than what can be handled easily.
I am not sure whether you would agree or not, in most situations whatever amount of work a facilitator tries to put in towards the end it is a thankless job, something which was implicitly expected from the facilitator.
I detect my burnout approaching when my regular 1-1 team member reviews highlight non-healthy behaviour or negative attitude surfacing on my part. Then its time for a quick break (physical, emotional and mental) from things and reflection, a reminder of the future success I am working for, and/or other "carrot" in the form of a ideal holiday planning session or taking session :)
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.
3 comments
Watch Thread Reply