Katherine Radeka, Author at High Velocity Innovation Page

Technical Excellence Accelerates Innovation by Enhancing Agility

March 15, 2021 by Katherine Radeka

Continuous attention to technical excellence and good design enhances agility. — Agile Principle #9

A well-designed Agile process for development pulls technical excellence from teams wherever it is applied, by making the Agile process more effective in ways that visibly benefit the team and the organization.

The astounding growth of DevOps, with better architecture standards, more automated tools for regression testing and the movement towards test-first development in software shows how this has manifested in software development, even among people who are hacking out a Minimum Viable Product for a startup.

I’ve also seen the same effects among teams using Rapid Learning Cycles.

Faster Innovation — Fewer Failures
The Promise of Rapid Learning Cycles

March 10, 2021 by Katherine Radeka

My controller, Shivaun is on a quest this month to find a new accounting system for us. We need to change systems because our current provider experienced a major product failure. They needed to replace some obsolete technology in their software to make them compatible with the latest Mac operating system — and they worked on that project for years. But ultimately, they were forced to admit that they simply could not get the new version out the door.

Sometimes people come to Rapid Learning Cycles because they have either experienced such a catastrophic failure or they see that they are at risk of one. Yet some innovation thought leaders think we should embrace failure to achieve speed. Why can Rapid Learning Cycles promise faster innovation — and fewer failures?

Healthy Product Teams Are Productive Product Teams

March 8, 2021 by Katherine Radeka

“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” – Agile Principle #8

Software teams that develop products in a waterfall style can turn into “death marches” at the end — and hardware teams that operate under the same flawed model end up in “production hell.”

This means that the accumulation of missed requirements and design flaws have turned into a cascade of late-found defects that have overwhelmed the team. They are behind schedule — often months or even years late. The pressure to deliver is overwhelming — and it breaks people, even if they don’t talk about it openly.

Spot Check: Rapid Learning Cycles for Deep Tech and Early-Stage Startups

March 3, 2021 by Katherine Radeka

For deep tech and other startups, the Rapid Learning Cycles framework provides a method to plan and execute research activities in a structured
way. — Jennifer Barnes. Former CEO and Co-Founder, Spot Check Technologies

For deep tech and other startups, the Rapid Learning Cycles framework provides a method to plan and execute research activities in a structured way. This case study describes how David Stokes of Technology Systems Ltd, a Rapid Learning Cycles Certified® Advisor, assisted this start up team during the earliest stages of their company.

This is the principle from the Agile Manifesto that trips up hardware developers the most. Of course, hardware developers are not delivering working software — so what is the closest equivalent? And why does it matter?

What Is Your Primary Measure
of Progress?

March 1, 2021 by Katherine Radeka

“Working software is the primary measure of progress.” – Agile Principle #7

« Previous Page

Tags

Search this site.