Corporate Revolutionary Library

Corporate Revolutionary Library

475 bookmarks
Newest
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
Advanced Topic - Agile Testing - Scaled Agile Framework
Advanced Topic - Agile Testing - Scaled Agile Framework
If you don’t care about quality, you can meet any other requirement. —Gerald M. Weinberg Agile Testing Note: This article is part of Extended SAFe Guidance and represents official SAFe content that cannot be accessed directly from the Big Picture. Agile Testing is an approach to systems and software testing that develops and tests systems in small increments, often developing tests before writing the code, Story, or Feature. Although traditional development often uses a deferred, big-batch testing approach, tests help elaborateRead more
·scaledagileframework.com·
Advanced Topic - Agile Testing - Scaled Agile Framework
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
Sprint Review: Much More Than Just A Demo
Sprint Review: Much More Than Just A Demo
Many of those practicing Scrum mistakenly call the Sprint Review a Demo. Is it just a matter of terminology? From my point of view, the Sprint Review is the most underestimated Scrum Event, and for many companies, its potential is yet to be revealed. It is true that the Demonstration or Demo is an essential part of the Sprint Review, but it isn't the only one.
·scrum.org·
Sprint Review: Much More Than Just A Demo
Capacity vs Velocity
Capacity vs Velocity
I'm currently the Scrum Master of a 10 developer strong team. We've adopted Agile/Scrum methodologies for some time now and are currently on our 53rd Sprint. Our stakeholders actively like to understand the output of story points in advance of a Sprint. This is currently done on a capacity basis working on a focus factor of 60%.
·scrum.org·
Capacity vs Velocity
5 Steps to Find Your Definition of Done (With Examples and Workflows) | Planio
5 Steps to Find Your Definition of Done (With Examples and Workflows) | Planio
There’s a saying in the music industry that the easiest way to ruin a song is to keep working on it. Add enough effects, extra guitar parts, or more cowbell, and you’ll turn Woody Guthrie into Guns N’ Roses. Knowing when a piece of art is “done” is subjective and often difficult to define. But...
·plan.io·
5 Steps to Find Your Definition of Done (With Examples and Workflows) | Planio