Maturity model
Depending on your business and goals, you can be satisfied with any kind of process. It is possible to use FTP for collaboration and deployment and be satisfied with it. But obviously the more ambitious your goals are, the more efforts you had to put into automation to reach technical excellence.
The table below should help you identify your processes maturity, possible problems, and potential for growth:
| Stage | 1 | 2 | 3 | 4 | 5 |
| Name | Gatekeeping | Cross-team | Integration | Starting | Mature |
|---|---|---|---|---|---|
| Typical time for idea to production | 1 year | 1 quarter | 1 month | 1 week | 1 day |
| Description | Functional groups are operating independently, Gatekeepers need to sign off for any stage | Conversations happens across teams, SCRUM & Agile | Teams consist of all relevant people, DevOps | Complete flow from idea to production | Teams prioritize and measure speed |
| Tools | SVN, Jira | Pull Requests(GitHub) or Merge Requests(GitLab) | CI/CD/Pipelines: Jenkins/GitLab | Chat/Chatops/IDE | Dashboard/Integrated set of tools |
| Structure | Not measuring from idea yet | Feedback comes from the systems instead of people. Removal of most meetings | |||
| Failure modes | Many projects are canceled before ever reaching production, Lots of time pinging gatekeepers to sign off, many swim-lanes. | Sprint is holy but what is made is not what is envisioned | Development is fast when it actually starts, long wait before items get scheduled | ||
| Organizations in this stage | GitLab Inc. |