Skip to content

Agile methodology

Posted on:September 23, 2022 at 03:22 PM

what is agile methodology

Waterfall was built for monolithic applications. It takes very long time to develop software.

Stages in waterfall model

Agile methodology

Agile menifesto

Agile principles

Agile frameworks

Scrum metrics and kpi

Kanban Trello jira

Sample columns in Kanban board

Workflow

One Kanban card per user story/work item.

Leadership at all levels, not just manager creating cards and moving them in a workflow.

Pull from right to left when there is bandwidth.

Create a board with stages and fill with cards at each stage.

Kanban card Title Description Owner Due date Label

When column bunchup they reveal a bottle neck in the workflow.

Flow

Lead time: time for card from start to done.

WIP limit: max no of cards in any column at a time.

Commitment point

Delivery point.

Kanban for IT: JIRA service desk Ticket raised becomes cards.

Kanban for sw development: Cards made in planning meetings based on what customer wants.

Could be combination of above two.

Card should take a day or two.

A day is 6-8 hours.

WIP limits: could be base of saying no to new projects. Obeying WIP limits increases efficiency.

WIP limit of column= no of people contributing to board @ × 1.5

Goals for Kanban Decrease lead time. Map wip limit to team’s specific skills. Reduce idleness. Protect healthy culture.

scrum

Process Ceremonies Artifacts

Scrum is agile project management framework team use to develop, deliver and sustain products.

Framework for continuously shipping value to customers. Framework to get the work done.

Handles changes in requirements market conditions etc. As not everything is known in advance.

Breakdown project into sprints.

Sprints: short iterative release cycles.

Product backlog: a running Todo list of features, user stories, bugs etc.

Every few weeks the teams selects items from backlog to work in next sprint.

Throughout a sprint team participate in number of events on regular basis called ceremonies.

Sprint duration: about two weeks.

User story: As a type of user, I want goal so that I receive benefit.

Ceremonies

Sprint planning: at the start of sprint.

Daily scrum or standup.: 15 minutes in the morning.

Sprint reviews: at the end of sprint to see what was accomplished. In a demo to product owner who approves.

Sprint retrospective.: At the end of each sprint to document what worked and what didn’t.

Scrum roles

Product owners: prioritize work, aware of business and market.

Scrum masters: scrum experts within the team. They coach po, dev team and business on the scrum process. Look ways to fine tune the practices. They are servant leaders.

Development team: team of Dev and designers who work towards sprint goals and tell po about the forecast of the sprint completion.

Scrum artifacts in each ceremony:

sprint planning

three steps in sprint planning. Backlog grooming, sprint planning meeting and creating action items.

Sprint planning session Leads to focus on executive, prevent surprises and ensures higher quality code.

Average velocity: amount of work completed in a sprint.

First decide sprint goal and velocity after that pick user stories from the backlog for the sprint.

Take verbal confirmation from the team and who is starting in which item.

standups

sprint review

sprint retrospective