Product Innovation, Agile Transformation, Design Thinking
I always struggle with the word “requirements”. This is how specifications and functionalities are normally called when working on a project. Requirements create a blanket of necessity and limit the empowerment of product managers to be effective at solving problems. The word requirement, and its verb counterpart to require, in their essence define something that is “required”, “needed”, “expected”. The
Books This is a short list of great books on Agile, Scrum, and practices to become an effective Scrum Master. Scrum and Agile foundations “Essential Scrum: A Practical Guide to the Most Popular Agile Process“, by Kenneth Rubin “Your Scrum Playbook“, Fabian Schwarts, CST “Scrum: The Art of Doing Twice the Work in Half the Time“, by Jeff and JJ
The Scrum Master role in Scrum is one of the most important and often misunderstood. The creators of Scrum, Jeff Sutherland and Ken Schwaber, recognized that change is hard and in order for teams to be able to effectively transition to a new way of working (adopting Scrum) help was required in terms of coaching and support. So the Scrum