week 4 - analyze and design

Flashcards covering Agile analysis, development lifecycle zones and lanes, and the process of seeding the product backlog.

Agile Analysis

Vertically divided into zones and horizontally into lanes within the Agile Development lifecycle.

Zones (Agile Development)

Vertical divisions in Agile analysis representing different activities, events, and artifacts.

Lanes (Agile Development)

Horizontal divisions in Agile analysis representing scenarios such as a quarter, a year, or the next 5 years.

Initiation and Planning (Zone)

Activities to plan and prepare for new product or epic development, including artifact preparation.

Seeding the Backlog (Zone)

Activities to create and prepare the initial set of epics, features, and user stories in the product backlog.

Quarterly Inception (Zone)

Activities to plan features and stories to be delivered within a specific quarter.

Iteration Inception (Zone)

Planning for 2-week sprints or iterations, particularly for teams using Scrum.

Daily Activities (Zone)

Ongoing iteration activities such as planning for the next iteration, refining the backlog of upcoming sprints, and daily standups.

Iteration Closeout (Zone)

Activities performed at the end of a sprint.

Quarterly Closeout (Zone)

End-of-quarter activities, including releasing the product or changes to production, supporting issues, and adapting for the new quarter.

Short Lane (Agile)

Applies to scenarios where planning occurs for the next quarter, Program Increment, or release, typically 8 to 12 weeks.

Long Lane (Agile)

Applies to scenarios where planning happens for 2 quarters to five years.

Grand Lane (Scaled Agile)

Applies to scaled agile organizations that include multiple collaborative product areas and agile teams.

Epic

A large work item requiring multiple teams over multiple quarters, presenting a high-level capability of the product.

Feature

A work item that can be completed in one quarter by one or more teams.

Initial Feature Limit (Backlog Seeding)

Recommendation to limit the initial set of features to 15 to 20 for a new product, as requirements may evolve over time.

Backlog Seeding Participants

Stakeholders who will benefit from features, Product Manager, Product Owners, Architects, Developers, Quality Assurance, and Analysts.

Methods for Discovering Initial Features

Field research, identifying reasons why a customer would purchase or use the product, or process modeling, identifying tasks in an end-to-end business process.