Digité products have been the core execution platform for many IT service companies in India. We have a leadership position in the market, given that 4 of the Top 5 India based IT service companies use our products.
First off, I have to say that I'm not 100% certain how I feel about Yuval's blog post. It feels like a forced comparison of apples and oranges. But in critically reading it, it forces me to think about why I feel that way. And as always, these are all just my opinions. No harm in sharing them, right?
One of the things that is very natural in Kanban but less so in Scrum implementations is the ability to deal with emergent or unplanned work during a Sprint.
We are happy to announce the release of SwiftEnterprise 4.0. It is the next generation of our SwiftALM product with the focus to deliver Enterprise Class Agility.
Inspired by Steve Porter's efforts to bring process practitioners closer together and educate Scrum practitioners, I'm writing a shadow series of posts that will follow the Kanban and Scrum - Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods.
One of the things that I see very often is a belief that Scrum and Kanban cannot work together and nothing is farther from the true. If we look at one of the core values of The Kanban Method you'll see that the first principle is:
Start with what you do now
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.
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.
