In this article we are going to discuss some of the very basic concepts of the SCRUM type of software development. These terms will help us in building better software for the different types of users and stockholders.
Writing the vision of the any organisation most specifically it is very important to write the vision from the view of the customer.
- Vision help us to understand where we want to be in next years.
- Vision help us to build the Roadmap for a specific thing.
- Working Software can help us to get the positive outcome from the customers.
Definition of Done
It helps to understand the Agile teams whether their software meets the quality bar or not.
- It can be a document Automatic Testing and Scalability.
- Helps the Teams to Minimize the Development cost and Debt.
The time span in weeks to complete a given task. It is better to have around 1-2 sprints in order to deliver the excellent and working solution to the good quality.
Sprint Backlog is the Prioritized list of work that is ready to being worked on from now on.
It is not guaranteed that it will be done but it will be priority to get it complete.
It is a kind of forecast not commitment.
Everything that time is looking forward to do. It is used to create sprint backlog. It is from starting to the medium term.
Definition of Ready
A document to team agreement, containing specific conditions and team conditions.
Very important role, and set by the organization for the best outcomes of the product or the software.
What and Why
What and Why
It is the Main and Basic thing that what we are building and why we are building that specific thing.
All kind of persons from UI/UX designers to the testers.
How and When
How we are going to meet the users requirements and when we are going for the release of the software and things like that are handled by the Dev Teams.
Product Owner is looking forward to the speed and the Dev Team is looking forward to the quality of the product so who controls the balance and the answer is the simple it is the SCRUM Master. He coaches the product owner and dev team.
Backlog Refinement / Backlog Grooming
Once the sprint is finished, the SCRUM Master and the Dev Team have a meeting in which they talk about what has achieved and what has not achieved and how to achieve efficiently what is left behind and how much time it will take. This process is called the Backlog Refinement.
- What can be deliver in the next sprint?
- How the work of next sprint can be accomplished?
It totally depends upon the historical performance and current performance of the teams.
A short meeting at the end of the day to discuss what have done today and how to synchronized the work that is going on and how to achieve the due work. The following three questions are generally asked at the daily SCRUM.
- What I did yesterday to meet sprint goal?
- What I will do today to meet sprint goal?
- What I should do tomorrow to meet sprint goal?
The sprint work will be presented to the customer what has been done till now and what is remaining and how we are going to achieve the remaining work. This is most likely a demo of the currently working product so that the owner can have a good look at the completed things.
The performance of the sprint is taken into account at the Retrospective phase. Here we have a look into what were the mistakes made and how we went with the structure of the team and what kind of effect technologies had on the sprint and what benefits we got by the means of the tools that were used during the sprint. Team will come up with a new plan for the improvement of the sprint.
I hope that these terms would have helped you in order to understand SCRUM better which is the very effective and useful software development technique which is being in used in most of the organisations.
Top comments (0)