Scrum Product Owner

A Refresher on A/B Testing
A Refresher on A/B Testing
A/B testing is a way to compare two versions of something to figure out which performs better. While it’s most often associated with websites and apps, the method is almost 100 years old and it’s one of the simplest forms of a randomized controlled experiment. This testing method has risen in popularity over the last couple of decades as companies have realized that the online environment is well-suited to help managers, especially marketers, answer questions like, “What is most likely to make people click? Or buy our product? Or register with our site?”. It’s now used to evaluate everything from website design to online offers to headlines to product descriptions. The test works by showing two sets of users (assigned at random when they visit the site) different versions of a product or site and then determining which influenced your success metric the most. While it’s an often-used method, there are several mistakes that managers make when doing A/B testing: reacting to early data without letting the test run its full course; looking at too many metrics instead of focusing on the ones they most care about; and not doing enough retesting to be sure they didn’t get false positive results.
·hbr.org·
A Refresher on A/B Testing
List of system quality attributes - Wikipedia
List of system quality attributes - Wikipedia
Within systems engineering, quality attributes are realized non-functional requirements used to evaluate the performance of a system. These are sometimes named architecture characteristics, or "ilities" after the suffix many of the words share. They are usually architecturally significant requirements that require architects' attention.[1]
·en.wikipedia.org·
List of system quality attributes - Wikipedia
The Three Pillars of Empiricism (Scrum)
The Three Pillars of Empiricism (Scrum)
Empiricism means working in a fact-based, experience-based, and evidence-based manner. Scrum implements an empirical process where progress is based on observations of reality, not fictitious plans. Scrum also places great emphasis on mind-set and cultural shift to achieve business and organizational Agility. The three pillars of empiricism are as follows:
·scrum.org·
The Three Pillars of Empiricism (Scrum)
The Effective Change Manager's Handbook: Essential Guidance to the Change Management Body of Knowledge - edited by Richard Smith, David King, Ranjit Sidhu, Dan Skelsey), APMG
The Effective Change Manager's Handbook: Essential Guidance to the Change Management Body of Knowledge - edited by Richard Smith, David King, Ranjit Sidhu, Dan Skelsey), APMG
The Effective Change Manager's Handbook helps practitioners, employers and academics define and practise change management successfully and develop change management maturity within their organization.
·a.co·
The Effective Change Manager's Handbook: Essential Guidance to the Change Management Body of Knowledge - edited by Richard Smith, David King, Ranjit Sidhu, Dan Skelsey), APMG
Determining Sprint Length
Determining Sprint Length
There is no one-size-fits-all, magic bullet for determining a sprint length that works well for every team. Originally, Scrum called for one-month sprints, but nowadays many teams have been successful with two-week or even one-week sprints. Choosing the right sprint length is about determining an appropriate stimulus-to-response cycle. In a sprint, the initial stimulus is the customer setting the priority of the stories. The response is the team building working software.
·mitchlacey.com·
Determining Sprint Length