Kanban Basics Reading List
Kanban 101 2014 02 kanbans not-so-hidden agendas 2 Kanban: Is it in the cards? – SD Times: Software Development News Crisp’s Blog » Kanban kick-start
Home » Blog
Kanban 101 2014 02 kanbans not-so-hidden agendas 2 Kanban: Is it in the cards? – SD Times: Software Development News Crisp’s Blog » Kanban kick-start
Scrum Reading List User Story Primer by Dean Leffingwell The 8 Stances of a Scrum Master | Scrum.org How to improve your Daily Scrum? Scrum
Agile Project Management Reading List Patton on Incremental Releases Who says release planning is not agile – Vered Yeret at Agile Israel 2015 Explaining Cumulative
Product Ownership 101 User Story Primer by Dean Leffingwell Professional Scrum Product Owner I | Scrum.org Jeff Patton on the Scrum Product Owner Role (19)
Over the past couple of years, my colleagues and I have led dozens of implementations in a variety of companies. As we closed the second year of our company we began noticing the problems and costs incurred by the fact that we each worked differently. E.g. miscommunications, differences in outcomes, and rework done between implementations. We decided it was time we go and analyze our past implementations for common goals and methods of operation.
How can you develop products in domains of extreme uncertainty?
How can you learn who will be the customers? What do the customers value? What will be a scalable and repeatable business model?
Learn about the new approach to discovering these critical aspects of a business using the latest techniques from the Lean Startup world (NOT just for Startups!!!). Based on the Lean Startup movement started by Eric Ries’ “Lean Startup” book.
Want to go Agile in an Agile way?Learn how Kanban is helping pragmatic organizations successfully achieve sustainable and sticky Agility without risky revolutions. What is
I will be talking about:
* The problems that we wanted to solve (some are still with us) and how the Kanban mindset helped us define the change and then implement it
* what challenges we encountered along the way
* what’s important (in my opinion) in this process
* what did we gain (so far) from implementing the change at Pelephone
Continuous Deployment sounds like a great concept, but is it applicable only to small startups? Can it be implemented also in organizations with complex production services and millions of users?
Request for additional information and prices