Adobe

Methodology

Kanban

which is under the Agile umbrella. The team maintains a single backlog and simply pull in the highest prioritized work item when the have availability. There are no sprints or long planning session.

"Miniature SDLC"

loosely resembles the entire Software Development Lifecycle (SDLC). Specifically, each campaign will have tasks that correlate with major phases of the SDLC: Analysis, Design, Construction, and Testing.

The following outlines the typical lifecycle:

• Idea and Feasibility

A test campaign originates on the business side from the product owners. The product owners will communicate their idea to the business.
At this point, the business will engage the development team to perform a high-level feasibility analysis.
The purpose of this analysis is to determine whether implementing the campaign is possible and what a high-level estimate on the complexity (small, medium, large) would be.

Keep in mind that the feasibility analysis is meant to be high-level and no formal requirements are drawn up at this stage.
The purpose of the feasibility analysis is purely to determine the complexity so that a decision can be made as to whether the campaign should be pursued further and what its priority should be.

• Analysis and Design

Once the feasibility analysis has been performed on a campaign, it will be placed on the backlog and its priority will be determined by the product owner.
When it's time for implementation, the business will provide a formal set of requirements in the form of a Sponsor Intake Form. Once this is received, the developer should perform a more detailed level of analysis and design for the campaign's implementation. The outcome of this analysis should be an approved tech commit.

• Construction

Once analysis and design has been completed, the developer may begin construction on the campaign.

• Testing

• Activation and Maintenance