Determine Readiness
Problem: You don’t know if the team is ready to release.
It’s not enough for the software to be ready. Your team needs to be ready, too. What good is making the code available if no one hears about it, or knows where to find it? What “ready” means can vary from project to project, but let’s look at a few areas that are likely to come up.
-
Release announcement. Do you have one written? Whether you send it via email, blog post, press release, or anything else, the release announcement is how most people find out about the release.
-
Website. For many projects, the website is how users find and download the new version. If the website needs to be updated to point to the new release (or use new screenshots), those need to be done ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access