Agile Complexification Inverter

Just imagine proper form and you can increase strength in your pinky finger 35%. Imagine Increased Muscle Strength!-Experiment In a fascinating experiment, researchers at the Cleveland Clinic Foundation discovered that a muscle can be strengthened just by thinking about exercising it. For 12 weeks (five minutes a day, five days per week) a team of 30 healthy young adults imagined either using the muscle of their little finger or of their elbow flexor. Dr. Vinoth Ranganathan  and his team asked the participants to think as strongly as they could about moving the muscle being tested, to make the imaginary movement as real as they could. Compared to a control group – that did no imaginary exercises and showed no strength gains – the little-finger group increased their pinky muscle strength by 35%. The other group increased elbow strength by 13.4%. What's more, brain scans taken after the study showed greater and more focused activity in the prefrontal cortex than before. The rese

What is the difference between a test and an experiment? I propose that in the 21st century and the realm of software development that these definitions must morph to our needs.  There is little difference in the general definition. Yet many people in quality control or quality assurance departments appear to dislike the word experiment.   Defining actions a person takes to perform a 'test-case' as an experiment appears to rankle feathers.   I find this interesting. Test - (verb) take measures to check the quality, performance, or reliability of (something), esp. before putting it into widespread use or practice. Experiment - (verb) perform a scientific procedure, esp. in a laboratory, to determine something. I would like to define that within the modern software world that the word test have a more specific meaning.  I propose: Test - (verb) a highly repeatable measure to check the quality, performance or reliability of (something), esp. before (something) is crea

A typical impediment sticky annotating the blocked task. Just making an impediment list is not good enough.  Yes, it is a start.  But only the start.  Raising impediments at the daily stand-up meeting shows that a team is mature enough to recognize that all problems are better solved in the light of day.  Problems are easier to solve when more than one person is working on the issue.  One of the first steps to getting multiple people working on an impediment is to make it known to the team. Yet this is the start, not the end of the process.  Yes many newbie teams believe that the Scrum Master's job is to resolve these impediments.  That is a wonderful misconception and will work for a while as the newbie team learns the power of an agile mindset.  But only the maturing teams learn that it is their job to remove these impediments. So what are 7 aspects on a great impediment card living on the top of your impediment list? Title - this should be a short pithy phrase; not a