What is scrum

What is scrum

Scrum is a very popular framework for implementing agile project management.
Although some people think that agile and scrum is the same thing, this is wrong.

While there are many frameworks for implementing agile, scrum is the most outstanding owing to its specific concepts and practices categorized into roles, timeboxes and artifacts.

Generally, the components of the scrum framework are:
1. Three roles: Product owner, scrum master and scrum development team
2. Sprints: A project iteration of less than a calendar month
3. Scrum events/ceremonies: Sprint planning meeting (what and how meetings), daily scrum meetings, sprint review meeting and sprint retrospective meetings.
4. Scrum artifacts
a) Product Backlog:
a prioritized backlog with end user requirements; the product owner is responsible for this
b) Sprint backlog: 
Elected items from the product backlog. It’s like a mini-plan for achieving the sprint goal and delivering the product increment👇.
Forecast the functionalities in the next increment and what needs to be done to deliver that functionality. The development team are responsible for this. 
c) Product increments:
At the end of each sprint, the new product increment should be in a functional state and meets the scrum team’s definition of “Done”. If all works well and the team’s estimation stays on track, the increment has all sprint backlogs’ items, meeting the team’s definition of done.


The Scrum Events:

Sprint planning meeting:  (Time Box: 8 hours for a one month sprint).
Planning Meetings are held at the beginning of each sprint which lasts a maximum of 8 hours (for 1 month sprints). It is attended by product owner, scrum master and scrum team.
The PO submits and describes the prioritized product backlog and explains to the team about the sprint goal and product backlog’s top items.
The team agrees on which prioritized items to complete during the upcoming sprint and then shifts these items from the product backlog to the sprint backlog.
Daily scrum meeting: (Time Box: 15 minutes)
Every day, during the sprint, the scrum master, scrum team and or product owner (optional) must attend a daily scrum meeting of less than 15 minutes.
During these day to day scrum meetings, the team members talk about what they worked on the previous day, what they’ll work on that day and identify any setbacks to progress.
This daily scrums synchronize the scrum team’s work plus their project knowledge, communication and decision making is enhanced.
Sprint review: (Time Box: 4 hours for a 1-month sprint)
At the end of each sprint, review, the team demonstrates the new functionality to the PO scrum master, customers and other stakeholders/sponsors interested in providing feedback that may perhaps influence the following sprint.
The relevant stakeholders express their impressions and clarify whether their user stories/requirements are well implemented. The PO ascertains whether the product is really “Done”. 
This feedback loop could lead to changes to recently released functionality or just lead to revising or adding items to the product backlog. 
Sprint retrospective meeting: (Time Box: 3 hours for a 1-month sprint)
The Sprint retrospective meeting is another event in scrum attended by the entire scrum team at the end of each sprint.
The entire team comes together to reflect on the sprint that has just ended as well as spot any improvement measures needed.
They generally talk about how to make their work more effective and efficient in the future.
While the sprint review is on the product, sprint retrospective meetings focus on the process.




Refrences

Paul VII. Agile Product Management: User Stories:  How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum (scrum, ... development, agile software development) (pp. 7-8). Pashun Consulting Ltd.. Kindle Edition. 

Comments

Post a Comment

Popular posts from this blog

Maxpooling vs minpooling vs average pooling

Image
Pooling is performed in neural networks to reduce variance and computation complexity. Many times, beginners blindly use a pooling method without knowing the reason for using it. Here is a comparison of three basic pooling methods that are widely used. The three types of pooling operations are: Max pooling: The maximum pixel value of the batch is selected. Min pooling: The minimum pixel value of the batch is selected. Average pooling: The average value of all the pixels in the batch is selected. The batch here means a group of pixels of size equal to the filter size which is decided based on the size of the image. In the following example, a filter of 9x9 is chosen. The output of the pooling method varies with the varying value of the filter size. The operations are illustrated through the following figures. Average, Max and Min pooling of size 9x9 applied on an image We cannot say that a particular pooling method is better over others generally. The choice of pooling operation is made
Read more

Percentiles, Deciles, and Quartiles

Image
Percentiles Percentile: the value below which a percentage of data falls. Example: You are the fourth tallest person in a group of 20 80% of people are shorter than you: That means you are at the  80th percentile . If your height is 1.85m then "1.85m" is the 80th percentile height in that group. In Order Have the data  in order , so you know which values are above and below. To calculate percentiles of height: have the data in height order (sorted by height). To calculate percentiles of age: have the data in age order. And so on. Grouped Data When the data is grouped: Add up all percentages  below  the score, plus  half  the percentage  at  the score. Example: You Score a B! In the test 12% got D, 50% got C, 30% got B and 8% got A You got a B, so add up all the 12% that got D, all the 50% that got C, half of the 30% that got B, for a total percentile of 12% + 50% + 15% =  77% In other words you did "as well or better than
Read more

Momentum

Image
Momentum Because mini-batch gradient descent makes a parameter update after seeing just a subset of examples, the direction of the update has some variance, and so the path taken by mini-batch gradient descent will "oscillate" toward convergence. Using momentum can reduce these oscillations. Momentum takes into account the past gradients to smooth out the update. We will store the 'direction' of the previous gradients in the variable  v v . Formally, this will be the exponentially weighted average of the gradient on previous steps. You can also think of  v v  as the "velocity" of a ball rolling downhill, building up speed (and momentum) according to the direction of the gradient/slope of the hill. Figure 3 : The red arrows shows the direction taken by one step of mini-batch gradient descent with momentum. The blue points show the direction of the gradient (with respect to the current mini-batch) on each step. Rather than just following the gradient, we let t
Read more