Embracing Agile¶

quick summary of agile practices

Definitions¶

Product backlog¶

• Features we want to implement but not yet prioritized for the release
• Often decided by the product manager/offering manager

Release backlog¶

• Features that we want to implement for a particular release
• Offering management along with engineering team collaborates to set the scope of a release

Sprint backlog¶

• User stories, specific tasks that need to be completed during a specific period of time
• Decided by the development team depending on the velocity and capacity

Epic¶

• Large body of work that can be broken down to a number of smaller stories
• Spanning across multiple sprints
• Commitment tracked over a release
• Evolves based on customer feedback and development progress
• No Pull Requests are made against an Epic

User Stories¶

• Informal, general explanation of a software feature/end goal written from the perspective of the end user or customer
• Spans across multiple days
• Commitment tracked over a sprint
• Does not change over a sprint

Sub tasks¶

• A set of specific outcome focussed activities that contribute to a Story's progress
• Spans across a few hours to a couple of days
• Commitment tracked over days
• Does not change over a sprint

Definition of ready¶

The criteria to move from new-issue to backlog:

• requirement is well defined in the user story following INVEST criteria
• Dev lead and dev team must have talked about the story at least once
• A least one acceptance criterio is explicitly defined
• Story is sized and prioritized
• Story must be brokent down enough to fit single sprint

Definition of Done¶

Describes the requirements that must be met in order for a story to move from In Progress/Review/QA to Done/Closed

Criteria

• Code is refactored and reviewed
• Code is integrated with master/main branch
• Automated tests (UT+FVT) are written and all tests are green
• Documentation changes are incorporated

Ceremonies¶

Zenhub practices¶