From 717cfaf537f75afb08876acd25ef3fe43a54991a Mon Sep 17 00:00:00 2001 From: abicky Date: Sun, 4 Dec 2022 23:28:52 +0900 Subject: [PATCH] Fix tip of "Production readiness" --- docs/lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lifecycle.md b/docs/lifecycle.md index 52116d9..b6c0cff 100644 --- a/docs/lifecycle.md +++ b/docs/lifecycle.md @@ -38,7 +38,7 @@ When preparing to initially release your service to production (i.e., to be cons * **Internal reviews.** Readiness checks of your service by other design phase stakeholders should occur prior to promotion into production. This can include things like information security audits, approval from the sustainability team(s), or any other reviews required by your organization. However, it's worth noting that these aren't necessarily "later-stage" or even "final-stage" reviews. These reviews can benefit greatly from being incorporated into your ongoing work. !!! tip - An example anti-pattern of collaboration would be to have a "hardening sprint" be the last last sprint of a project, when all security tests are performed and identified issues may or may not be fully remediated. In contrast, performing these reviews continuously throughout the entire development phase would surface information security concerns at a time when they're likely much less integrated in the service and, therefore, more difficult to remediate. + An example anti-pattern of collaboration would be to have a "hardening sprint" be the last last sprint of a project, when all security tests are performed and identified issues may or may not be fully remediated. In contrast, performing these reviews continuously throughout the entire development phase would surface information security concerns at a time when they're likely much less integrated in the service and, therefore, easier to remediate. ## Runtime Launching a service into production requires far more than just ensuring availability. Day-to-day operation of your service requires maintenance, iteration, and deploying updates. Services are never "done." Any service that is actively consumed to a reasonable degree—especially those newly launched—requires ongoing improvements, either to address new features requested by customers, resolve newly discovered software bugs, or improve issues such as security or reliability. The following areas of concern should be addressed throughout the runtime phase of a service.