Scrum or Kanban? Pick One And Get On With Delivering Quality Code!
Jason Gorman is pesting about the fact that some individuals in the Agile community are obsessing about project management and applying specific methods. He suggests that energies should be directed at delivering quality code instead since this is much harder to master that the simple Scrum or Kanban methodologies.
He is right on.
Speaking of Scrum and Kanban, you may also want to read my previous post.
[via Parlez UML]
Kanban – The Next Step in the Agile Evolution?
I am interested in everything that can help improve my teams' productivity and consequently helps us provide better value to our customers. As such, I have started reading about Kanban, a project management methodology that appears to "compete" with Scrum. Scrum is the methodology that I am currently using.
Scrum is an iterative method that provides incremental value to stakeholders at the end of each iteration. The product owner provides requirements at the beginning of each iteration. During the iteration, the team designs, implements, tests, documents, debugs new features based on those requirements. At the end of the iteration, the team demonstrates the new features to the product owner who accept or reject them.
Kanban on the other hand, is not an iterative process. The product owner provides ranked list of requirements. The team pulls requirements from top of the list one at a time. The team designs, implements, tests, documents, debugs new features based on those requirements. The product owner review the new features as soon as they are produced.
Project Management Hut presents an article describing Kanban as the next step in Agile Evolution.
