Skip to main content

What is Scrum? Why Scrum and Who is Scrum for? - By Ankur Mistry

What is Scrum?Scrum is one of the most popular Agile Framework, It's a mindset, an approach to turning a complex project into something workable.

Scrum is adaptive, Speedy, flexible, Iterative and effective.
 
Scrum Development designed to deliver a significant chunk of product in short cycle, quickly Iteratively with Continuous feedback and Continous Improvement and adaption to change.

An empirical process is generally used for dealing with large and complex project development where the definition of the requirement is not so clear or well defined, Scrum falls under Empirical Process where Transparency, Inspection, and Adaption are 3 Pillars of Empirical Process.
 
 Image Credit: en.wikipedia.org
https://zacharysexton.com/wp-content/uploads/2014/04/Scrum-Pillars.jpgWhy Scrum?The key strength of scrum is Scrum Team, which is self-organized, Cross Functional and Self Motivated.

Following are the 10 key points why we should use Scrum. 
  1. Effective and Timeboxed Development processScrum is timeboxed all events in scrum are time-boxed, it's minimizing the unimportant work so that the efficiency is high.
  2. Continuous DeliveryAt the end of every sprint, all the completed stories would be delivered or added to a potentially shippable product as frequently as the customer requires.
  3. Continous Feedback and Continous ImprovementsCollaboration with the client at all stage of development so Continous feedback from client helps the team to Improves product delivery.
  4. Early Delivery of Most Valuable RequirementWith Scrum, we can start early delivery with the most viable products will helps the client to capture the market first.
  5. MotivationThough Scrum Team is Self-motivated, Daily Standups and Retrospective Sprint processes give greater levels of motivation among the team.
  6. Faster Problem ResolutionCollaboration and Cross-functional teams are the key points for faster problem-solving. The team will work together so great level of trust and be knowing each other they will solve problems faster.
  7. Effective Deliverables
    Regular Backlog Grooming and refinement process and Prioritized Product Backlog process helps effective deliverables to the client.
  8. Customer Centric
    Scrum is more Customer-driven, that aides on business esteem and having a collective way to deal with the issues encourages the group to distinguish the issues and it's determination at a beginning time of a venture.
  9. High Trust Environment and Collective Ownership
    Conduct Daily Standup and Retrospective meetings gives transparency and collaboration, prompting a high trust workplace guaranteeing low grinding among representatives.
  10. Innovative EnvironmentThe Retrospective meeting creates an environment of learning and adaptability prompting an imaginative and inventive workplace.
Who is Scrum for?Scrum can be used in any complex environment, doesn't matter if you are working on your Website, Web Application, a smartphone application, e-commerce website for a store or planning an event.

Scrum has the ability to change extend administration over each industry, each business, and even in Daily lifestyle. By using Scrum, you'll turn out to be more Agile and more focus and by staying focused, collaborating, and communicating, you can achieve what truly needs to be done - Successfully.

As I said earlier Scrum is a mindset so you can fit the framework anywhere.

"Scrum is easy, Solving problems with Scrum is challenging. - Ken Schwaber"

Reference
  • https://www.scrumalliance.org/
  • https://www.scrumstudy.com 
  • https://thenounproject.com/

Comments

Post a Comment

Popular posts from this blog

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed  Agile Story Point Estimation  and  Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allow...
Post a Comment
Read more

Retrospective Meetings By:Namrata Parik

This article talks about the least important meeting in a Sprint, the retrospective meeting, at  least as considered by the business and sometimes also by the developers. It is often considered to be a waste of time and given the least priority, and sometimes even omitted if there are time constraints. In fact it is the most important meeting but does not show any immediate business value. Talking about my own experience, we were newly into the project and the geek in the team was not getting enough technical tasks to devour, resulting in not so good documentations by him and his general disinterest in the team. This was discussed in the retrospective and his problem was faced, assessed and solved within a span of two weeks (a single Sprint), and he was given enough tasks to fulfill his coding appetite, resulting in better output by the entire team. Talking about retrospective techniques, the most effective way to conduct a retrospective is the Timeline Review. The te...
Post a Comment
Read more

Scrum Framework - 5 Events in Scrum Framework - By Ankur Mistry

In my previous articles, we have discussed  3 Roles  and  3 Artifacts  in Scrum. In this article, we are going to discuss 5 events in the Scrum Framework. There are Five events in Agile Scrum Framework. Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint ( Figure: Life cycle of Scrum from  http://www.agiletroop.com/product/life-cycle-of-scrum/ ) Sprint Planning  is the event in which the Product Owner presents the ordered product backlog to the development team. As the word suggests, 'Sprint Planning' means we are going to plan the work to be done in the Sprint. There are two main parts - 'What' and 'How'. 'What' can be done in this Sprint? 'How' will the selected work get done? What can be done in the Sprint - In this part, the Product Owner presents the product backlog items with high business value tasks as a first priority to the development team. All team members collaborate to understand ...
1 comment
Read more