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 Mark Levison on Apr 29, 2008
Is your team juggling conflicting requests? Is your Product Owner struggling to decide which customer's to serve and which to ignore for now? Does it seem that everyone has a different agenda?
In "Make Your Mission Possible" Johanna Rothman, Management Consultant, suggests that the lack of a mission statement is making it difficult for your team to say no. Johanna tells a story of company whose sales staff promise additional reports with understanding that this is exactly what the team doesn't need.
In the story Janice, the manager and her team leads discuss the work they do now and other work that they think needs to happen in the company (even outside of their group). Next they examine the work that they're doing but don't think they should. Based on all of this they right a mission statement that says:
A good mission explains what we do and don't do. It establishes the boundaries of our work and explains how our development group fits into the organization. A great mission will provide reasonable and measurable objectives for our work so other groups can see what we are responsible for--and not responsible for.
Along the way Johanna's suggests that we don't write promises of 24hr turn around into the mission statement unless there is staffing and organizational support for it.
In Got Mission? Neil Bourgeois, a Software Developer, observes that most mission statements are written by the wrong people. Neil believes that a team should write its own mission statement helps the team take ownership of it. In Neil's case his PM brought the team together for a brainstorming session to help them
In Neil's case many of Agile values popped out during the first two parts, for example Communication, Feedback, Simplicity, Responding to Change, Customer Collaboration. In the end the team crafted a mission statement "Positively impact every project."
18 agile and lean practices for effective software development governance
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!
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.
No comments
Watch Thread Reply