Kanban and "the art & science of visualization"

 A wise man once said-
 Agile is more than just standing up and burning down!

 Talking of KANBAN, one of the key principles is – Visualize the flow of work


In other words,  "manage work instead of people".

It says "people tend to manage people because it's visible. If the work cannot be seen, the human nature tends to measure what can be seen, but that doesn't make it the right thing to measure"

 




   Best,
   Jasdev Singh (Scrum Servant)



Comments

Post a Comment

Popular posts from this blog

When you equate story points with time...

Image
Agile becomes fragile! When you are "doing" agile (most likely because it's in vogue) but have not come out of the "sequential " SDLC execution syndrome or the traditional waterfall way of thinking and executing a project, you are most likely headed for a disaster! Of many things that may or will go wrong, is the estimation of work . The traditional methods of estimation like function-point analysis helped us answer the question - "how long (or duration) will a piece of work take to complete?". On the contrary, Agile keeps it simple and takes a minimalistic approach to estimation. In my opinion, estimation in agile is no rocket science as long as you are clear with the basics and understand "what story points are" and how to use them. Visit my blog post on story points for an understanding. Story Points vs. Time (Person Days) Mike Cohn shares a mantra that makes estimation easy - " Estimate size, measure velocity, derive ...
Read more

What's the point in a story point?

Image
Part 1: talking of the point Story points are estimates of effort as influenced by the amount of work, complexity, risk and uncertainty ( https://www.mountaingoatsoftware.com/blog/what-are-story-points ). When we estimate with story points, we assign a point value to each item. The raw values we assign are unimportant. What matters is the  relative values . A story that is assigned a 2 should be twice as much as a story that is assigned a 1. It should also be two-thirds of a story that is estimated as 3 story points. Not delving into the details of how to estimate and what these numbers should be (linear vs. non-linear series or Fibonacci numbers), the focus of this post is to discuss how these points affect the life of a scrum team (development team, scrum master & product owner). A story adds “value” by delivering functionality that the business has asked for, and can/will use depending on whether the story is a part of potentially...
Read more

Is it simple to practice theory?

Theory vs. practicing the theory Part 2: challenges in practicing agile theory So … we looked at the agile manifesto and the “people side” of things that it talks about in part 1 of “theory vs. practicing the theory”. The second part focusses on - What makes agile theory difficult to put into practice? We’ll get a better understanding if we start by looking at who’s involved in software development using agile methodology (and I’ll stick to scrum here to keep it simple). Here are the key players –   The three roles in scrum : product owner (PO), scrum master (SM) and the develop ment team Various management roles (you can’t do away with management, can you?) – project manager, program manager, delivery manager, engagement manager or whatever name you like to give to that “authority” Business stakeholder(s) or those representing the market Project/program sponsor(s) putting their money into the venture Looking at the list of key players above, it do...
Read more