{"id":5741,"date":"2019-01-30T12:33:48","date_gmt":"2019-01-30T07:03:48","guid":{"rendered":"\/?p=5741"},"modified":"2019-12-31T16:10:57","modified_gmt":"2019-12-31T10:40:57","slug":"scrum-framework-or-methodology","status":"publish","type":"post","link":"https:\/\/www.argildx.us\/miscellaneous\/scrum-framework-or-methodology\/","title":{"rendered":"Is Scrum a Framework or Methodology?"},"content":{"rendered":"
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.<\/p>\n
<\/p>\n
Scrum is not a fully-featured project management methodology. Rather, it describes an approach to Agile management with a focus on project teams, short “sprints” and daily stand-up meetings.<\/p>\n
While it borrows the principles and processes from Agile, Scrum has its own specific methods and tactics for dealing with project management.<\/p>\n
“Agile is the philosophy and Scrum the methodology. While Scrum is agile, agile isn\u2019t scrum.”<\/em><\/p>\n The Scrum approach places the project team in front and center of the project. Often, there is no project manager. Instead, the team is expected to be self-organizing and self-managing. This makes it ideal for highly focused and skilled teams, but not so much for others.<\/p>\n Besides these, it has all the benefits of Agile – rapid iteration and regular stakeholder feedback.<\/p>\n The Scrum approach is best for highly experienced, disciplined and motivated project teams who can set their own priorities and understand project requirements clearly. It has all the flaws of Agile along with all its benefits. It works for large projects but fails if the project team itself is very large.<\/p>\n Below diagram depicts the core values of the Scrum framework.<\/p>\n Below diagram depicts various roles and their correlation in the Scrum framework.<\/p>\n \u00a0 Various roles that comprise of scrum framework are:<\/p>\n A Scrum Master is a team leader and facilitator who helps the team members to follow agile practices so that they can meet their commitments. The Scrum Master is responsible for ensuring Scrum is understood and enacted.<\/p>\n A Scrum Master serves the Scrum Team<\/p>\n Below diagram depicts the misunderstood stances of a scrum master<\/p>\n <\/p>\n Stances of a scrum master<\/p>\n <\/p>\n Stances of a scrum master are:<\/p>\n It is the team which works for SDLC of the application. This team includes developers, testers, technical lead, product owner and scrum master. Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of \u201cDone\u201d product at the end of each Sprint. Only members of the Development Team create the Increment.<\/p>\n A Product Owner drives the product from business perspective and is the one who decides and defines requirements, prioritize their values and release dates. Product owner is also involved in iteration planning and release planning meetings.<\/p>\n The product backlog is a list of all the product features generally defined by \u201cuser stories\u201d. User stories define everything potential users want to do on the site. There are many tools to keep track of your project backlog, both analogue and digital options. Agile projects are broken down into small, consistent time intervals. These intervals are referred to as sprints. A sprint has a time duration of 1 – 3 weeks depending on the extent of the overall project. Before each sprint, there is a sprint planning meeting. This meeting determines what the goals are for that sprint. Based on the team velocity, a set of features are pulled from the top of the backlog. During the sprint, no features are added, and the sprint goals don\u2019t change<\/p>\n This is the first meeting of every sprint and the amount of work which can be achieved in the sprint is decided in this meeting depending on the team velocity. User stories are assigned to the dedicated team as per the requirement and analysis.<\/p>\n <\/p>\n Every morning of the sprint the project team gets together for a short (under 15 minute) meeting. This meeting takes place at the same time every day and includes everyone on the project.<\/p>\n Each person on the team is tasked to answer 3 simple questions:<\/p>\n At the end of every sprint, A Sprint Retrospective meeting takes place with a functional demo of the user stories that has been completed during the sprint. The sprint review meeting brings together the project team and other project stakeholders like the client to present the work that was completed.<\/p>\n Event<\/strong><\/p>\n<\/td>\n Time-box for 1 Month<\/strong><\/p>\n<\/td>\n<\/tr>\n Development Team<\/p>\n<\/td>\n 3 hours<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Why should Scrum be used? What is Scrum? Scrum is not a fully-featured project management methodology. Rather, it describes an approach to Agile management with a focus on project teams, short “sprints” … Read more<\/a><\/p>\n","protected":false},"author":21,"featured_media":7295,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[317],"tags":[116,117,118,119,1747],"yst_prominent_words":[1744,1738,1737,1729,1734,1742,1741,1218,1731,1735,1736,1740,1748,1728,1730,1732,1743,1745,1733,1739],"acf":[],"yoast_head":"\n<\/p>\n
<\/a>Advantages of Scrum<\/h5>\n
\n
<\/a>Disadvantages of Scrum<\/h5>\n
\n
<\/a>Scrum is best for<\/h5>\n
<\/a>Scrum values<\/h5>\n
\u00a0
<\/h1>\n
<\/a>Commitment<\/h5>\n
\n
\n
<\/a>Focus<\/h5>\n
\n
<\/a>Openness<\/h5>\n
\n
<\/a>Respect<\/h5>\n
\n
<\/a>Courage<\/h5>\n
\n
<\/a>Roles, Artifacts, and Events in the Scrum Framework<\/h5>\n
<\/strong><\/p>\n
<\/a>Roles<\/h5>\n
<\/a>Scrum Master<\/h6>\n
\n
<\/p>\n
<\/p>\n
\n
Scrum Master as a Servant Leader<\/strong><\/h6>\n
\n
Scrum Master as a Coach<\/strong><\/h6>\n
\n
\n
\n
\n
Scrum Master as a Facilitator<\/strong><\/h6>\n
\n
\n
Scrum Master as a Teacher<\/strong><\/h6>\n
\n
Scrum Master as a Mentor<\/strong><\/h6>\n
\n
\n
\n
\n
Scrum Master as a Manager<\/strong><\/h6>\n
\n
Scrum Master as a Impediment Remover<\/strong><\/h6>\n
\n
Scrum Master as a Change Agent<\/strong><\/h6>\n
\n
Scrum Master Service to the Product Owner<\/strong><\/h6>\n
\n
Scrum Master Service to the Development Team<\/strong><\/h6>\n
\n
Scrum Master Service to the Organization <\/strong><\/h6>\n
\n
<\/a>Scrum Team<\/h5>\n
\n
<\/a>Product Owner<\/h5>\n
\n
<\/a>Artefacts<\/h5>\n
<\/a>Sprint Backlog<\/h5>\n
\n
<\/a>Product Backlog<\/h5>\n
\nAfter all user stories are created, they are ranked based on the priority and grouping on the stories. Grouping is done based on the inter-dependencies of the stories<\/p>\n<\/a>Events<\/h5>\n
<\/a>Sprint<\/h5>\n
\nSprints are time-boxed iterations that serve iterative-incremental development.<\/p>\n\n
\n
\n
The entire point of Scrum Framework is to create a Done increment<\/strong><\/h6>\n
<\/a>Sprint Planning<\/h5>\n
<\/p>\n
<\/a>Daily Scrum<\/h5>\n
\n
\n
<\/a>Sprint Review\/ Retrospective Meeting<\/h5>\n
\n
\n
<\/a>Scrum events quick reference<\/h5>\n
\n\n
\n \n Inspection<\/strong><\/td>\n Adaptation<\/strong><\/td>\n Who Attends<\/strong><\/td>\n \n \n Sprint Planning<\/strong><\/td>\n Product Backlog<\/td>\n Sprint Goal, Forecast, Sprint Backlog<\/td>\n Scrum Team<\/td>\n 8 hours<\/td>\n<\/tr>\n \n Daily Scrum<\/strong><\/td>\n Progress toward sprint goal<\/td>\n Sprint Backlog<\/td>\n \n 15-minutes (always)<\/td>\n<\/tr>\n \n Sprint Review<\/strong><\/td>\n Increment, Sprint, Product Backlog<\/td>\n Product Backlog<\/td>\n Scrum Team Stakeholders<\/td>\n 4 hours<\/td>\n<\/tr>\n \n Sprint Retrospective<\/strong><\/td>\n Sprint<\/td>\n Actionable and committed improvements<\/td>\n Scrum Team<\/td>\n \n