Skip to main content

Scrum Framework

Agile is a popular software development methodology use today. Scrum and eXtreme Programing (XP) are two types of agile methodology. Sutherland (in Lacey 2012) states that 75% of the agile software development use Scrum framework and around 17% of the scrum team use XP engineering practices. Scrum framework looks extremely simple however it is found to be hard to implement effectively.

Scrum is a lightweight and simple process framework used for developing complex products. It is not a process, methodology or engineering practices.

Scrum's 5 Core Values


  • Focus
  • Respect 
  • Commitment 
  • Courage 
  • Openess 

Scrum Project Roles

  • Scrum master - The scrum master works as a facilitator of the team. He ensures that the team is functioning as expected. 
  • Product owner - The product owners is the person who drives the project. 
  • Scrum Team - Team who actually do the development. 

Scrum Artifacts

  • Product backlog - This artifact consists of all the select requirements that need to be met. The requirements are sorted according to its priority. 
  • Sprint backlog - The requirements stated in the product backlog is grouped into Sprints so that it can be completed in 2-4 weeks. This artifact consists of the requirements that is to be met on a particular sprint
  • Burndown chart - This chart provides the current status snapshot during a scrum project. It shows amount of work that needs to be completed and the time remaining. In 2011, it was agreed that burndown charts are not mandatory artifacts.

Scrum Meeting

  • Release planning - This meeting is carried out before starting a sprint. For that sprint that is n weeks long requires n x 2 hrs of release planning. 
  • Daily Scrum meeting - This is 15 minute stand-up meeting that is carried out daily at the start of day. The purpose of the meeting is to facilitate free communication and understandings among team members. Three important questions discussed by each team members are:
    • - What I did yesterday?
    • - What I will do today?
    • - What are possible obstacles that I face today?
  • Sprint Review - This meeting is conducted after the completion of a sprint. In this meeting the client feedback is the most important. In other words, client is expected to approve the product released. 
  • Spring Retrospective - This meeting is more internal to the Scrum team and product owner is kept out of this meeting. Possible questions addressed in this meeting are:
    • - What went well in last sprint?
    • - What needs improvement?

References


  • Lacey M 2012, The Scrum Field Guide, Practical advice for your first year, Addison-Wesley. Foreword by Jeff Sutherland.






Labels:

Comments

Post a Comment

Popular posts from this blog

A Comprehensive Evaluation of the Internal Consulting Process: Steps and Considerations

Introduction Internal consulting has emerged as a critical function within organizations, offering in-house expertise to solve complex business problems and drive change. It closely mirrors external consulting in methodology but is differentiated by the consultant's intimate knowledge of the organization and a vested interest in its long-term success. This article aims to evaluate the key steps involved in the internal consulting process, offering insights into each phase's significance and challenges. Steps in the Internal Consulting Process The internal consulting process can generally be segmented into five distinct stages: Initial Assessment, Data Collection and Analysis, Solution Development, Implementation, and Evaluation. Below is an evaluation of each step: Step 1: Initial Assessment Objective: To understand the problem or opportunity area and define the scope of the project. Significance: A well-defined scope ensures that the consulting project stays focused and manage...
Post a Comment
Read more

The Evolving Landscape of Consulting Practice: Changes and Implications

Introduction Consulting is a field that thrives on its ability to adapt to market demands and emerging trends. As businesses evolve due to technological advancements, shifts in consumer behavior, and fluctuations in global markets, consulting practices must keep pace. This article explores some of the significant changes currently transforming the consulting industry and discusses their implications for both consultants and clients. Technological Disruption Data Analytics and Artificial Intelligence Consulting firms are increasingly integrating data analytics and artificial intelligence into their service offerings. These technologies allow consultants to offer data-driven insights that can significantly enhance strategic decision-making. This evolution means consultants now need skills in data interpretation and analysis, alongside their traditional expertise in business strategy. Virtual Consulting Platforms The advent of digital platforms enables consulting services to be offered re...
Post a Comment
Read more

The Imperative of Transition Structure in Implementing Change and A Model for Effective Transition

Introduction Organizational change is an inevitable phenomenon in the dynamic business landscape of today. While the conception of change is significant, its successful implementation is even more crucial. One key factor that often determines the success of implementing change is the presence of a well-designed transition structure. This article aims to discuss the necessity of having a transition structure in place and proposes a model to effectively guide the transition during organizational change. The Need for a Transition Structure Aligning Stakeholders Any significant change involves a variety of stakeholders, from senior management to front-line employees. A transition structure ensures that all parties are aligned, understand their roles, and are committed to the objectives of the change. Mitigating Risks Change often comes with risks, such as resistance from employees, potential loss in productivity, or lapses in quality. A structured approach can help mitigate these risks by ...
Post a Comment
Read more