Books
-
Kanban: Successful Evolutionary Change for Your Technology Business
The book provides specific and useful guidance to those attempting to adopt kanban management in software development.
The books is very well written and presents the material in a very easy to digest manner. It is so packed with information it is very difficult to mine even a significant portion of the value in one read. The organization allows for easy reference as you need to focus on any specific topic to find that topic and get an excellent review in minutes.
Articles
-
Making the Business Case for Agile Management
 
view details
"Agile Management seeks to make a paradigm shifting change in the approach to management of software engineering using best practices in management science including the true definition of value, the concept of a value chain, systems thinking and a focus
-
Stretching Agile to fit CMMI Level 3
 
view details
"At Microsoft, we've adopted the teachings of W. Edwards Deming and stretched our MSF for Agile Software Development method to fit the requirements for CMMI Level 3. The resultant MSF for CMMI Process Improvement is a highly iterative, adaptive planning m
-
CMMI or Agile: Why Not Embrace Both!
 
view details
40 page report from the Software Engineering Institute. "The purpose of this report is to clarify why the discord need not exist and to ask for your help in making the software development community aware that, when properly used together, CMMI and Agile
-
Why do we use Kanban?
 
view details
"(1) Evolutionary, incremental change with minimal resistance
(2) Achieve sustainable pace by balance throughput against demand
(3) Quantitative Management and emergence of high maturity behavior in alignment
with senior management desire to have a hig
-
Thoughts on how Kanban Differs from Scrum
 
view details
"Kanban uses the WIP limit as its control mechanism to provoke conversations about change. Failure to respect the WIP limits and discuss problems will lead to stagnation and a failure to improve. Improvement discussions are objective as the visualization, measurement, explicitness of policies and the models from Lean, Theory of Constraints and the teachings of W. Edwards Deming, allow a team to scientifically analyze their problems and propose solutions."
-
The Principles of the Kanban Method
 
view details
Use the 5 Core Properties."
1. Visualize the workflow
2. Limit WIP
3. Manage Flow
4. Make Process Policies Explicit
5. Improve Collaboratively (using models & the scientific method)"
-
How an automotive secret can make for better software
 
view details
"Kanban is still in the very early stages of adoption. It is true that most people in the software industry have never heard of it. However, there are many hundreds of companies on 5 continents already doing it. Some have very large, successful and well documented implementations. Firms such as the BBC in London, Globo and Petrobras in Brazil, Amdocs in Israel, Vanguard is a well known American adopter."
-
How an automotive secret can make for better software
 
view details
"Kanban is a way of visualizing invisible knowledge work activities such as software development, and limiting the quantity of work in progress. Limiting work-in-progress has several benefits: by avoiding over-burdening, quality is often significantly higher, while workers are happier and better motivated; delivery times are usually significantly shorter and far more predictable; priorities are often clear and prioritization decisions are simplified...
Deming’s work is core to everything we do. I think his book, The New Economics, is a seminal work in management thinking... If I could have coffee with just one of these process and management science pioneers it would be Deming."