8

Common Practices to follow in Agile

 3 years ago
source link: https://blog.usejournal.com/common-practices-to-follow-in-agile-956ff2e1a174
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Common Practices to follow in Agile

Agile values, principle and common practices

“As an Agile coach, you don’t need to have all the answers; it takes time and a few experiments to hit on the right approach.” — Rachel Davies and Liz Sedley (Agile trainers and authors)

1*Kq5UogKDLWyMcjNxTT1UzQ.png?q=20
common-practices-to-follow-in-agile-956ff2e1a174
Image Source: scrummaster.dk

AGILE INTRODUCTION

Agile is a mindset defined by values, guided by principles, and manifested through many different practices. The Four Values of the Agile Manifesto are listed below:

  1. Individuals and Interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

The 12 clarifying Principles flowed from above values are listed below:

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is face‑to‑face conversation.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.
  • Simplicity — the art of maximizing the amount of work not done — is essential.
  • The best architectures, requirements, and designs emerge from self-organizing teams.
  • The team regularly reflects on becoming more effective, then tunes and adjusts its behavior accordingly.

If we are following the Agile methodology, then we should know the Common Agile Practices and implement it.

Want to read this story later? Save it in Journal.

COMMON AGILE PRACTICES

  1. Daily Standup Meeting

This is a 15-minute time-boxed eventfor the development team to plan for the next 24 hours. In this meeting everyone answers the following questions in a round-robin fashion
a. What did I complete since the last standup?
b. What am I planning to do today?
c. What are my impediments (any blockers, risk or problems)

TIP: Encourage any team member to facilitate the standup instead of a project manager or leader to ensure it does not turn into a status meeting, but instead is used as a time for the team to self-organize and make commitments to each other

2. Backlog Preparation

As the product owner or requirement analyst gather the requirement then they might create a product roadmap to prioritize the order of feature to develop which show the anticipated sequence of deliverables over time. From these requirements, story tickets are created and presented to the team

3. Backlog Refinement

In this meeting, the product owner present the story or tickets which are created and discuss with the team member to know about the potential challenges or problems in the story. It helps team member to understand what stories are coming up in the development. Mostly, this meeting is for 1 hour and conducted in mid of a 2 week iteration

TIP: Consider using impact mapping to see how the product fits together. Under normal circumstances, the product owner leads this work. A servant leader can facilitate any necessary meetings as a way of serving the project.

4. Sprint Planning

This meeting is conducted before starting the sprint to determine and assign the stories to the team as per their capacity. By reviewing the team size and their capability (can take the reference of velocity chart to understand how much story point the team can complete), task is assigned which they are going to do for this sprint.

TIP: Draw the team’s attention to the antipattern and help the team to discover how to improve its standups

5. Retrospectives

According to the official definition from the Scrum Guide: “The Agile retrospective is the opportunity for an Agile team to examine itself and define a plan for improvement to be enacted during the next Sprint”. During this meeting, the team discuss about
a. What went well in the sprint?
b. What could have been better?
c. What are the action items that need to be done?

6. Sprint Demo

In the demo session, the team demonstrates all the completed task at the end of the iteration. This meeting can bring out the valuable feedback, suggestion and discussion about developed stories. A fundamental part of what makes a project agile is the frequent delivery of a working product. A team that does not demonstrate or release cannot learn fast enough and is likely not adopting agile technique.

Above are some common agile practices. Following the Agile methodology in the right way, will surely gonna make positive impact in the productivity and the growth of the company.

Reference:
Agile Practice Guide Book published by PMI
and many more website articles.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK