Agile process -Part -II .
- khyati sehgal
- May 24, 2014
- 2 min read
In continuation of my last post where I discussed what are the roles of the teams in the Agile process, here I am going to discuss how agile helps in software development. Also how to actually start with agile software development.
The process focuses that there should be continuous interaction between team members. There are several terms which one should know before getting the knowledge of the process.
Sprint
This is an iteration wherein all development, testing, discussions happen. It is of fixed time like 1 week, 2 weeks, 3weeks, etc. It has a specific goal to achieve that depends on the scope of sprint.
Backlog
This has all the stories that are to be included in the future sprints or releases.
Sprint Story
This is a TO-DO task with specific business value, with a clear scope. Each story has some end functionality and feature.
Sprint Tasks
Each story is further divided into small tasks. These tasks can be of any number and format.
Story point
Each story is calculated depending upon its complexity, time is taken to do it, etc, And this is added to each story as a story point of it. Story points are always given to stories in the Fibonacci series pattern, 0,1,1,2,3,5,8,…
Sprint velocity
For each Sprint a total calculation of story points as a whole determines the velocity of that Sprint.
This process has to drive by various meetings, let’s discuss them.
Sprint Planning
All the stories are traversed in the backlog and some stories according to the priorities of stories are taken into consideration. Here all team member estimates the stories and gives story points to each story.
Sprint planning
Sprint — Daily stand-ups
In this each team member has to state three details of them :
What he/she has done yesterday
What he is planning to do
What is he doing? Or any blocker if he/she is facing any.
Sprint — Daily stand-ups
Scrum of scrums
In this, each team’s Scrum Master collaborates to get an update of each team.
Scrum of scrums
Sprint review
This is the demonstration part where each team shows the work they have done within this sprint. It takes place at the end of each sprint.
Sprint review
Sprint retrospective
This is the open space where the team talks on 3 areas:
Sprint retrospective
This happens after the Sprint Retrospective and before the demo of the next sprint.
This is a process in which we can directly call BA within and outside the team, We can manage frequent calls to PO for a better understanding of the product. We can pair with User Acceptance Team for testing and thinking bigger as a customer perspective.
So all in all, unlike traditional models this approach has more interaction, more teamwork, a closer picture of the end product, and a lot more.
Комментарии