Comments on: Make Your Process Workflow Explicit http://toolsforagile.com/blog/archives/178 Tue, 07 Sep 2010 21:14:19 +0000 http://wordpress.org/?v=2.9 hourly 1 By: siddharta http://toolsforagile.com/blog/archives/178/comment-page-1#comment-103170 siddharta Tue, 04 Aug 2009 10:43:25 +0000 http://www.silverstripesoftware.com/blog/archives/178#comment-103170 Hi David, I'm not advocating that managers impose a workflow, rather look at what you are already doing and make it visible. If you are doing build and test in a single step, then by all means keep it as a single stage in the workflow. The problem arises when you are doing a workflow in practice, but its implicit and not made visible. Nice blog post btw. Like the use of cumulative flow graphs. They are very useful indeed. Hi David,

I’m not advocating that managers impose a workflow, rather look at what you are already doing and make it visible. If you are doing build and test in a single step, then by all means keep it as a single stage in the workflow. The problem arises when you are doing a workflow in practice, but its implicit and not made visible.

Nice blog post btw. Like the use of cumulative flow graphs. They are very useful indeed.

]]> By: David Draper http://toolsforagile.com/blog/archives/178/comment-page-1#comment-103169 David Draper Tue, 04 Aug 2009 10:23:35 +0000 http://www.silverstripesoftware.com/blog/archives/178#comment-103169 In the most part I agree. In fact I blogged a few weeks ago on visualising these workflow steps outside of the sprint. <a href="http://www.agiledesign.co.uk/scrum/managing-wip-with-scrum/" rel="nofollow">here</a>. On the other hand we do need to take care to retain the workflow within the sprint as property of the team. I have invited teams to describe their workflow, even make it visible if it helps them. But they must own it and be free to change it over time. I see a risk with the current enthusiasm for Kanban that managers are taking back workflow and Kanban as a means for directing the team. Fortunately, so far I have seen no evidence of this, it's just a niggling concern. Regards Dave. In the most part I agree. In fact I blogged a few weeks ago on visualising these workflow steps outside of the sprint. here.

On the other hand we do need to take care to retain the workflow within the sprint as property of the team. I have invited teams to describe their workflow, even make it visible if it helps them. But they must own it and be free to change it over time.

I see a risk with the current enthusiasm for Kanban that managers are taking back workflow and Kanban as a means for directing the team.

Fortunately, so far I have seen no evidence of this, it’s just a niggling concern.

Regards

Dave.

]]>