The approach
How we work on it
- Write down the current release steps and their failure points.
- Automate build and test on every change.
- Deploy through a gated, manually approved step with a backup first.
- Keep the pipeline definition in source control.
What you receive
Typical deliverables
- Pipeline definitions
- Build and test automation
- Gated deployment with approval
- Release and rollback runbook
What we will and will not promise
Automation does not make a risky change safe by itself. We keep a human approval and a backup before production changes.
How an engagement runs
Discover, propose, deliver, support
The same four stages apply to every Incipit practice, so you always know what has been agreed and what happens next.
- 01
Discover
We learn the business need, the people who will use the result and the constraints, before any solution is proposed.
- 02
Propose
Scope, milestones, responsibilities and ownership are agreed in a written proposal.
- 03
Deliver
Work is built in milestones. You review working builds and approve each stage before the next begins.
- 04
Support
Handover of code and documentation as agreed, with maintenance and support available afterwards.
Technology
What we build with
- ASP.NET MVC
- C#
- Entity Framework
- SQL Server
- Microsoft Azure
- Android (Kotlin)
- Bootstrap
Questions
Before you enquire
Related work
Where Incipit has done this
Related services
Describe what you need
Tell us the requirement and your time zone. We reply with questions, options and a written proposal.