Moving from traditional project management to agile is a paradigm shift. From push to pull systems from a control-and-command culture to a trust culture where authority is delegated. A good structure with some control mechanisms will most likely help you get the wanted results quicker. This article discusses the role that management plays in organizations that have decided to adopt agile.
An interview with Gojko Adzic, David Evans and Tom Roden on why they wrote this book, how quantifying quality can support testing, balancing trust levels when testing large and complex systems, why automating manual tests is almost always a bad idea, on using production metrics in testing, how to reduce or prevent duplication in test code, and on upcoming books in the fifty quick ideas series.
Little’s Law helps teams that use user stories for planning and tracking project execution, with a project buffer to manage inherent uncertainty of a fixed-bid project and protect its delivery date. 4
Dean Leffingwell’s “Leading SAFe LiveLessons” - training videos are based on Lean-Agile transformation concepts at enterprise level.
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.
Are you in the process of moving applications to a public cloud? In this article, we’ll explore four stages in a cloud migration lifecycle and the questions to answer before exiting each one. 1
An interview with Craig Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility.
Claudio Perrone talks about continuous evolution, servant leadership, popcorn flow (continuous evolution through rapid experimentation), and doing experiments to make change more continuous.
Finding ways to eliminate root causes of delays can improve flow. This article discusses clustering blockers and provides ways to prioritize blockers that have most impact or are the quickest wins.
How do you get good flow? A common scenario in a software company is that too much is going on at once. We need a shift in mindset, to go from focus on resource efficiency to focus on flow efficiency.
With talented developers, quality advocates and user-experience designers, teams know how to deliver valuable software. But as we improve service delivery using kanban, who manages flow?