Continuing our theme of facilitating Scrum and Kanban, we’re honored to publish another guest blog post by Dave White on ‘Kanban and Scrum Together – Not So Fast’.
Here Dave white has shared his thoughts on the article ‘Kanban and Scrum Together’ written by Steve Porter. Hope you enjoy reading it!
0
SwiftALM 3.2 is here! This release is focused on enhancing your experience on the Mobile App. Use the Voice search on your Mobile App's Search bar to easily search for a workitem. View summary of the timesheet routed to you for approval on the Mobile App in a whole new way.
In part 2 of this series, Christophe looks at the very Swedish phenomenon of Kanban going “man-cold”! As teams implement their early Kanban boards, they inevitably face the reality of the gap between what they are actually used to doing vs. what they put on their Kanban board. (We have posted about this phenomenon earlier as well!) Here, Christophe explains why this happens – and what to do about it quickly so as to not fall into the Policy Debt-trap!
Is this you? That is, does the question below, which I answered on a technical forum recently, describe a situation you might be facing or may have faced in the past? We have a brownfield project which was recently struck by disaster (many people leaving for unrelated reasons, too many new customers, much too large backlog for much to few people, etc.). Management support is still fine. Thank bob the product owner (decades of knowledge) is still here.
In Sweden, we love to ‘fika’. Fika requires you to take time to sit down and sip coffee (usually strong and black) with your colleagues to chitchat about this and that. Visiting different organizations, I tend to fika a lot and hear all these stories about how things are going.
“My team is using Kanban board but they seem to prefer to collate a couple of tickets then 'do a release' as appose to releasing each ticket. i.e. they move tickets through the workflow and then put them in a waiting column for days on end and then they do sporadic releases.
This post extends further on the possibilities of Portfolio Kanban for Enterprise Transformation, building on your reading of the previous posts in this series. In the first post, we discussed a key bottleneck to enterprise transformation, exploring the merits of Portfolio Kanban in addressing this in the second post, defining mandatory characteristics of fit-for-purpose tooling to improve success in the third post.
Continuing our theme of helping Agile teams understand the Kanban Method, so they can effectively adopt it for their improvement efforts, I am again honored to publish a guest article by another great friend of ours - Dave White. Dave is a Principal Consultant at Depth Consulting Ltd, and Program Director of the KCP Program at the Lean Kanban University.
This year’s Nobel for Economics has gone to the Behavioural Economist Richard Thaler. Richard is a Distinguished Professor at the Chicago Booth Business School. His big work is the influence of clues and society on individual decision making and actions.
Recently, there was an interesting problem posed on a project management discussion board. The questioner asked - “I have recently joined a company and to one of the projects that I'm engaged we have this Scrum team that has a mixed backlog (USs and Bugs).
