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

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres
Post a Comment
Read more

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum.  What is Agile Agile is a  Method  of project management that is characterized by dividing module in to tasks and t asks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method.  What is Scrum Scrum is an incremental agile software development framework  (Agile Framework).   Agile Scrum Process in Short. Product Backlog:  A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog. Sprint Planning:  In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list. Setting Capacity and Sprint:  Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User. Scrum Master’s role:  Is to make sure team focused on its goal. End of the sprint:  
Post a Comment
Read more

The Burn Up Charts In Scrum By: Namrata Parik

I would like to propose a less-taken path in my maiden article to track the progress in scrum. We usually do it using the burn down chart which is relatively easier to understand as compared to the burn up chart. These charts help the team and stakeholders to see and track the progress at any point in the release process or sprint. Burn-down chart provides us the information showing the progress based on the remaining hours or story points from top to bottom. (The burn-down chart can be plotted using story points, task count or the remaining effort) This chart is a plot of expected remaining and actual remaining, this is the most used chart in scrum and since it has only two lines it is considered to be a simple chart. It does not cover the scope creep. So sometimes what might look like ‘no work ‘ done by the team may actually be a result of scope creep. The chart below reflects that the team has not done any progress in Sprint 5 and 6 as the story points remain the same. Image
Post a Comment
Read more