Home / BA / Agile and Scrum

Agile and Scrum

Agile and Scrum:-

            Agile is a software development methodology, which has not required any documentation.

Agile is a light weight process tool, it can be implemented where faster delivery is required.

The main values of AGILE methodology are:

  • Individuals and interactions over processes and tools.
  • Working software over comprehensive documentation.
  • Customer collaboration over contract negotiation.
  • Responding to Change over following plan.

In this methodology documentation is not required. As it has no documentation process the customer retention is high for this process.

The main advantage of implementing Agile methodology is it will accept change requests any time. We can accept the change requests in middle of project and starting and completion of project.

Based on current scenario change is must based on customer attitudes, tastes and preferences. And also change request arises based on technological advancements in the market. To cope up with the technological changes in the market one should ready to accept the change immediately. Hence the Agile methodology is most acceptable process in software development life cycles. As it is accepts change requests in any time.


It is a framework. The framework begins with a simple basis. Start with what can be seen or known. After that, track the progress and tweak as necessary. The three pillars of Scrum are transparency, inspection and adaptation.

The frame work, is a part of Agile software development. When it comes to product development, Scrum roles include product ownerScrum master and Scrum development team.

Product owner:

The product serves as the liaison between the development team and its customers. The product owner is responsible for delivering completed product as expected.

Scrum master:

This team member acts as a facilitator. The Scrum master is responsible for ensuring that Scrum best practices are done and the project is move forward.


Scrum development team:

This group is works together for creating and testing incremental releases of the final product.

The Scrum process:

The Scrum can be implemented either beginning of the project or when we observed that the project is running behind schedule.Communication is an important part of the process. The communication is carried out through meetings, called Events.

 Scrum Events include

1.      Daily Scrum Meeting

2.      Sprint Planning Meeting

3.      Sprint Review

4.      Sprint Retrospective.

Daily Scrum Meeting:

                The Daily Scrum is a short stand-up meeting that conducted at the same place and time each day. In every meeting, the team discusses about work that was completed in the previous day and decides what work will be done in the next 24 hours. This is the time for team members to speak out about any hurdles that might prevent project completion.

Sprint Planning Meeting

                This happens at the beginning of each sprint and team decides on what they will be delivering in the sprint.

Sprint Review:


Sprint Review Meeting. In Scrum, each sprint is required to deliver a potentially shippable product .So at the end of each sprint, a sprint review meeting is held. During this meeting, the Scrum team shows what they accomplished during the sprint.

Sprint Retrospective:

 Sprint Retrospective meeting is conducted after Sprint ends. During this meeting, everyone reflects on the Sprint process. An important goal of a Sprint Retrospective is continuous improvement.

Scrum artifacts:


Product backlog,

Sprint backlog,

Product increment

Burn-down charts


Product backlog:

It is defines as all user stories that is all the requirements of the client.

Sprint backlog.

This is a list of tasks that must be completed before selected product backlog items can be delivered. These are divided in to time-based user stories.


 The burn-down is a visual representation of the amount of work that still needs to be completed. A burn-down chart has a Y axis (work) and an X axis (time). Ideally, the chart illustrates a downward trend, as the amount of work still left to do over time burns down to zero.

About Ram Teja.V

Check Also

What is the requirement elicitation? Have you ever participated in these elicitation meetings?

Introduction Requirement elicitation is a critical process in the field of business analysis. It involves …

Leave a Reply

Watch Dragon ball super