Well, maybe not my life, but my project’s life. A bit reading and patience will allow me to explain. But first, a definition of the word: Kanban. kanban |ˈkänˌbän| – noun a Japanese manufacturing system in which the supply of components is regulated through the use of a card displaying a sequence of specifications and [...]
If you’re using kanban in your environment, you probably use a cumulative-flow diagram. It’s a handy tool to track kanban metrics like cycle time and to quickly see bottlenecks. In addition to all the kanban goodness it gives you, it can also double as a timeline that you can use in your retrospectives.
Software projects very rarely both come in on time and budget and satisfy their end users. Its much easier to satisfy one of the above conditions, either living according to your original plan or adapting to the changing needs of your users. Satisfying both requires a certain amount of prescience. Demarco and Lister list Schedule Flaws as one of their 5 Risks of Software Project Management. In this article, we’ll discuss several symptoms and causes of schedule flaws, present metrics and diagrams that can be used to track your team’s progress against its schedule, and describe Agile ways to address this risk.
In a recent retrospective, our team identified a lack of satisfaction in our standup meetings. Some days they provided too much information; other days, not enough. Our meetings lacked a certain energy. Brian Button suggested a way for each of us measure our satisfaction with the standup meeting. To do this, we posted a big [...]