Implementation project and agile development: How two worlds meet in IT projects
One of the common misunderstandings in projects where Architecture and Agile development meet is the question: “Why do we need so many documents and artifacts?” At first glance, the implementation project and the agile backlog may seem to be duplicates. In fact, they are two layers of one ecosystem that complement each other and ensure successful delivery of the solution.
Implementation project: guarantee of scope and compliance with the contract
The implementation project is a formal document required by the contract and the Public Procurement Act.
It includes:
- functional requirements (FR), non-functional (NFR) and other (OR),
- a catalog of Use Case scenarios,
- architectural models and integration relationships,
- GAP analysis (As-Is vs. To-Be),
- a schedule and milestones,
- acceptance criteria,
- a risk register.
The purpose is clear: to show the customer and regulatory authorities that the solution is complete, has a clear framework, and can be objectively adopted.
Agile development: how big requirements turn into deliverable steps
On the other hand, there are development teams that need to work with requirements differently – breaking down large units into smaller tasks:
- Epic = larger business goal (e.g. “Patient Management”),
- User Story = specific user scenario (“As a doctor, I want to see a graph of values to assess a trend”),
- Acceptance Criteria = testable conditions,
- Technical Tasks = developer work (e.g. indexes, API contracts, logging),
- Sprint Backlog = work plan for the next sprint.
The purpose of the backlog is to ensure that the project moves incrementally, in functional steps, and that each deliverable meets the „Definition of Done“.
Traceability: a bridge between worlds
The key element that connects both worlds is the traceability matrix.
It ensures:
- that each FR/NFR/OR from the implementation project has its place in the backlog,
- that no requirement „disappears“ and is traceable to test and acceptance,
- that the customer is sure that the contractual scope is transferred to development.
Why is this model important?
- Management sees that the implementation project covers everything that is required in the contract and legislation.
- Development teams have smaller, manageable tasks that they can work with agilely.
- The customer gets the assurance that the resulting solution will meet their needs, schedule and regulatory obligations.
Summary
The implementation project and the agile backlog are not competitors, but partners.
- The implementation project answers the question “What exactly are we delivering and how will it be managed?”
- The agile backlog answers the question “How will we deliver it step by step?”
Combining both approaches creates an environment that is transparent for the customer, manageable for management, and at the same time agile and efficient for developers.
