20 Lessons From Introducing High Quality Software
This summarizes the main points from the 4 articles.
This summarizes the main points from the 4 articles.
It’s not just “a process.” It’s how you show respect for the time, energy and money committed by real people to your project.
Second in a series about building and launching high-quality software.
The first in a series about what it takes to build and introduce a quality software product.
Whatever you learn from a coach, the value comes from what you do every day.
“Growth hacking” associated with start-ups has the familiar ring of time-honored shared responsibility across corporate teams for growth of the company.
A readiness to tailor the organization to meet the evolving needs of the business is more promising than changing structures and titles or abolishing them altogether.
Working on multiple projects at once keeps you and your team sharp and agile.
Keep in mind the distinction between “planning” and “the plan.”
Sometimes the best sparks to creativity come from constraints. Look for opportunities to harness the hidden energy inside what appears to be a stumbling block.