Process Sheet D · delivery
Follow one feature from a sentence to a release.
Every feature we build takes the same path: a written scope, a branch, one pull request, automated tests and review before the merge, testing in the running app, then the release path agreed for the project.
- Sheet
- D · Process
- Unit
- One feature
- Steps
- 6, in order
- Checks
- Tests · review · the running app
- Release
- Agreed for each project
D-01 The path of one feature
Six steps. Choose one to see what it leaves.
What this step leaves
D-02 What progress looks like
One pull request per feature.
A pull request is the unit of progress. It carries the change, the automated test results, the review, and a written result from using the feature in the running app.
When one is merged, the feature goes out through the release path agreed for the project.
- Written scopeWhat the feature does and how we will know it works.
- Automated testsRun on the pull request.
- ReviewThe change is reviewed before the merge.
- Tested in the running appA written pass or fail, on a simulator, a device or a browser.
- ReleaseThe merged feature goes out through the agreed release path.
D-03 What happens, and when
Each step leaves a written record.
Before the build
The scope
A short written scope for each feature: what it does, who it is for, and how we will know it works.
During the build
Pull requests
One per feature, each with its tests, its review and its result from the running app.
After the merge
Release
How builds reach testers and users is agreed for each project.
We run our own products the same way: Aanaadu, Dosefolder, Panchangamanam and Palaka Balapam are each built through pull requests with automated checks and review.
See a sample plan for your app →Start a project
Tell us what you want to build and which platforms you need, or send the scope you drew. We reply by email.
hi@cr8veworks.com