Scope
The workstream, exclusions, repository boundary and acceptance evidence.
How the pod works
Three engineers working as one delivery unit.
The three engineers share the scope, acceptance evidence and review record.
Proposal fields
Six fields that make the engagement inspectable.
Assigned engineers
Each person, their relevant experience, role and responsibilities.
Working arrangement
Overlap hours, review cadence and attendees, acceptance evidence and escalation path.
Continuity
Planned absence cover, replacement process and client approval for substitutions.
Handover
Code and configuration, review record, acceptance evidence, operating notes, open risks and the client owner after handover.
Commercial terms
Start date, initial term, monthly fee, invoicing terms and notice period.
Research and releases
External evidence informs the method.
We use published software-engineering research to shape how we test, review and deliver code. We also track official releases and advisories for technologies in scope.
The source type, finding, practical implication and limitation are recorded on the research page.
See the research and release notesClient inputs
Decisions the client retains.
For each assigned engineer, the proposal records implementation decisions they may make and decisions reserved for the client.
Approvals
Who approves the proposal.
The proposal records the Anystack approver, client approver, version and date.
Engagement options
From delivery history to an engagement.
Review selected work or start a scoping conversation. The proposal records the scope, assigned people, responsibilities, review points and handover.