“Kanban is not a software development lifecycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process.”
“We’ve come to recognize that Kanban is giving permission in the market to create a tailored process optimized to a specific context.
Kanban is giving people permission to think for themselves. It is giving people permission to be different: different from the team across the floor, on the next floor, in the next building, and at a neighbouring firm.” – David Anderson
#kanban, #softwaredevelopment #projectmanagement 

"If you want to adapt new behaviours, your mindset needs to be congruent with those behaviours. If your mindset doesn’t support the new behaviours, ultimately your mindset will trump your behaviour and you won’t be able to get the results or sustain the change you want."

- Roger Schwarz

One won't become a systems thinker by reading System thinking books. I remember Craig Larman handing me Peter Senge's book during my Valtech days in 2004. This was as part of the reading list during the initial days of LeSS related experimentation. Even though, I read it many times, it all started making sense, when we introduced the ideas around "Multi team Product Backlog Refinement", and "Having shared visual spaces", etc.   These small ideas which were created to enable the teams to get the wholistic view of the product, helped me in connecting the dots with the knowledge from the various theories. I found it very helpful approach to practice and get your hands dirty from the things you have learned either through the book or training.  LeSS also recommends to "Own" an idea rather than "Rent" it.  If you are keen to learn more about how to own an idea rather than renting it, and also, the difference it could make to your product  development,  please register for my upcoming LeSS courses in Perth, Melbourne or Sydney: Perth: bit.ly/Perth_LeSS Sydney: bit.ly/Sydney_LeSS Melbourne: bit.ly/Melbourne_LeSS #productdevelopment #training #systemsthinking #less #renttoown

 

  

 

In the 1940s and '50s, when automation was increasingly applied, many began to worry that it would make people in general, and managers in particular, obsolete. If machines could replace people's minds as well as their muscles, what would ultimately be left for people to do? This concern was based on the incorrect assumption that there is a finite number of problems to which the human mind can be applied.  The problems that can confront human minds are unlimited. No matter how many are solved, an infinite number will always remain to be solved.  -  Ackoff  #SystemsThinking,#Ackoff,#LeSS,#management,#Thinking

In the book, "Competing against time" the authors found that reducing lead times to customers by three-fourths resulted in a firm moving to a growth rate that was two to four times the industry growth rate.  #lean  #less #agileleadership #leadtimereduction  

Register for "Certified LeSS Practitioner: From Principles to Practices" courses in Perth, Sydney and Melbourne.

Click on the link below to register:
Perth: August 1st - 3rd --> bit.ly/Perth_LeSS
Sydney: August 15th - 17th --> bit.ly/Sydney_LeSSbit.ly/Sydney_LeSS
Melbourne: August 29th - 31st --> bit.ly/Melbourne_LeSS


#LeSS #training #agile #scrum

Poor management can easily destroy collaboration by rewarding people for behavior that optimizes for their function at the expense of customer outcomes or wider organizational goals. Examples of this include rewarding developers for features that are “dev complete” but not production ready, or rewarding testers for the number of bugs they find.  In general, rewarding people for output rather than system-level outcomes leads to dysfunction, and in any case monetary rewards or bonuses have been demonstrated to reduce performance in the con- text of knowledge work

 - Jez Humble  

#optimization #features #testers #bonus #output #less

Certified LeSS Practitioner: From Principles to Practices 


Register for "Certified LeSS Practitioner: From Principles to Practices" courses in Perth, Sydney and Melbourne.


Click on the link below to register:

Perth: August 1st - 3rd --> bit.ly/Perth_LeSS
Sydney: August 15th - 17th --> bit.ly/Sydney_LeSS
Melbourne: August 29th - 31st --> bit.ly/Melbourne_LeSS
  
#LeSS #training #agile #scrum

 

Another great nugget by Ken Rubin 

"Many product development organizations focus more on eliminating the waste of idle workers than on the waste of idle work. For example, in traditional thinking, if I hire you to be a tester, I expect you to spend 100% of your time testing. If you spend less than 100% of your time testing, I incur waste (you’re idle when you could be testing).  

  

To avoid this problem, I will find you more testing work to do—perhaps by assigning you to multiple projects—to get your utilization up to 100%. Unfortunately, this approach reduces one form of waste (idle-worker waste) while simultaneously increasing another form of waste (idle-work waste). And, most of the time, the cost of the idle work is far greater than the cost of an idle worker."  #waste #productdevelopment #less #testers #utilization #idle