Search

Making The Move To Agile With Scrum - How Scrum Supports Agile

We should probably start clarifying what is the relationship between the two. Let's put it this way:Agile is the mindset, the WHATIt is not about ‘doing’ Agile but being Agile.Scrum is the framework, the HOWIt is one of the available frameworks most used to become more Agile.The Agile Manifesto tells us that it values the items on the left more than the items on the right:Individuals and interactions over processes and toolsWorking software/product over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planScrum defines specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes. This aims to get the most out of uncertainty.So the question is, how is Scrum supporting the Agile principles?(1) Individuals and Interactions over processes and toolsThe Scrum team members work together to achieve a shared business goal. The set of roles (Product Owner, Scrum Master & Development team) and how these are 'played' / contribute to each sprint is the key to success.Each individual within the Scrum team has a high responsibility and ownership towards the goal: from refinement of the work (backlog items), to their estimates, which are actually committed (sprint items), removing obstacles, optimising the backlog, definition of what a 'Done' item means.To enable the interactions in a consistent manner, Scrum framework uses:Sprint Planning - To discuss items of most value, clarify, decide which to commit to the Sprint, breakdown some tasks which enables seeing different approaches / points of view for the very same item.Daily Sprint - For progress transparency, collaboration, ownership, clarification, obstacles and team alignment.Review - Open to all stakeholders where the 'potentially shippable product' is transparently reviewed, demoed and new possible increments may arise. The review is the 'what', the deliverable tangible concept.Retrospective - Internal for the Scrum team where openly the 'how' is reviewed, to determine what could be changed that might make the next imminent sprint better.The Agile principle of Individuals and Interactions is supported by the 3 pillars of Scrum: Transparency, Inspection & Adaptation.(2) Working software/product over comprehensive documentationScrum requires a working, finished product increment as the primary result of every sprint which the team had chosen and commit to it at the start of the sprint.Even that the increment may not be 'shipped', the team’s job is to ensure the functionality is delivered by the end of the sprint as a 'potentially shippable product' which could go to market.During the sprint, the team works together, cross-skilled, with continuous testing, focusing on the defined goal to be achieved.Agile values the working product more. A quick note on documentation, avoid long winded documents no one will read, think of it with your Agile hat on: modular, iterative, easy to digest and reuse.Agile principle of Working product is supported by the Scrum pillar of Inspection.(3) Customer collaboration over contract negotiationMore often product reviews (including demos) enable more often feedback, and the frame on the event sets an open and transparent environment, so that the increment of product is being delivered early and often.The role of Product Owner is the key here to work closely with the business to prioritise the possible future increments by value (return on investment, refinement, size, risks etc)Collaboration is supported by the Scrum pillar of Transparency. At the beginning of the sprint you have a very open and clear prioritised committed items into the Sprint and the Review openly show what was accomplished and a place to highlight obstacles that may have disturbed the flow within that cycle.(4) Responding to change over following a planScrum is based on empiricism (inspect and adapt) which uses feedback loops to cope with complexity and risk. Scrum emphasises decision making from real-world results rather than speculation.Empiricism is a theory that states that knowledge comes only or primarily from sensory experience.As new information is discovered, the team updates the backlog, adapts towards the goal and constantly responds to change to deliver what has been committed as a 'possible shippable product'.Responding to change is supported by the Scrum pillar of Adaptation. Out of the 12 Agile principles, personally if I had to choose one it will be “Reflect regularly, tune & adjust to become more effective”, Retrospectives are the key to this. Only the organisations following this will keep up with the future.
Rated 4.0/5 based on 68 customer reviews

Making The Move To Agile With Scrum - How Scrum Supports Agile

221
Making The Move To Agile With Scrum - How Scrum Supports Agile

We should probably start clarifying what is the relationship between the two. Let's put it this way:

Agile is the mindset, the WHAT
It is not about ‘doing’ Agile but being Agile.

Scrum is the framework, the HOW
It is one of the available frameworks most used to become more Agile.

The Agile Manifesto tells us that it values the items on the left more than the items on the right:

  1. Individuals and interactions over processes and tools
  2. Working software/product over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

values the items in Agile
Scrum defines specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes. This aims to get the most out of uncertainty.

So the question is, how is Scrum supporting the Agile principles?

(1) Individuals and Interactions over processes and tools

The Scrum team members work together to achieve a shared business goal. The set of roles (Product Owner, Scrum Master & Development team) and how these are 'played' / contribute to each sprint is the key to success.

Each individual within the Scrum team has a high responsibility and ownership towards the goal: from refinement of the work (backlog items), to their estimates, which are actually committed (sprint items), removing obstacles, optimising the backlog, definition of what a 'Done' item means.

To enable the interactions in a consistent manner, Scrum framework uses:

Sprint Planning - To discuss items of most value, clarify, decide which to commit to the Sprint, breakdown some tasks which enables seeing different approaches / points of view for the very same item.

Daily Sprint - 
For progress transparency, collaboration, ownership, clarification, obstacles and team alignment.

Review -
Open to all stakeholders where the 'potentially shippable product' is transparently reviewed, demoed and new possible increments may arise. The review is the 'what', the deliverable tangible concept.

Retrospective -
Internal for the Scrum team where openly the 'how' is reviewed, to determine what could be changed that might make the next imminent sprint better.

The Agile principle of Individuals and Interactions is supported by the 3 pillars of Scrum: Transparency, Inspection & Adaptation.


Scrum Framework

(2) Working software/product over comprehensive documentation

Scrum requires a working, finished product increment as the primary result of every sprint which the team had chosen and commit to it at the start of the sprint.

Even that the increment may not be 'shipped', the team’s job is to ensure the functionality is delivered by the end of the sprint as a 'potentially shippable product' which could go to market.

During the sprint, the team works together, cross-skilled, with continuous testing, focusing on the defined goal to be achieved.

Agile values the working product more. A quick note on documentation, avoid long winded documents no one will read, think of it with your Agile hat on: modular, iterative, easy to digest and reuse.

Agile principle of Working product is supported by the Scrum pillar of Inspection.

(3) Customer collaboration over contract negotiation

More often product reviews (including demos) enable more often feedback, and the frame on the event sets an open and transparent environment, so that the increment of product is being delivered early and often.

The role of Product Owner is the key here to work closely with the business to prioritise the possible future increments by value (return on investment, refinement, size, risks etc)

Collaboration is supported by the Scrum pillar of Transparency. At the beginning of the sprint you have a very open and clear prioritised committed items into the Sprint and the Review openly show what was accomplished and a place to highlight obstacles that may have disturbed the flow within that cycle.

(4) Responding to change over following a plan

Scrum is based on empiricism (inspect and adapt) which uses feedback loops to cope with complexity and risk. Scrum emphasises decision making from real-world results rather than speculation.

Empiricism is a theory that states that knowledge comes only or primarily from sensory experience.

As new information is discovered, the team updates the backlog, adapts towards the goal and constantly responds to change to deliver what has been committed as a 'possible shippable product'.

Responding to change is supported by the Scrum pillar of Adaptation. Out of the 12 Agile principles, personally if I had to choose one it will be “Reflect regularly, tune & adjust to become more effective”, Retrospectives are the key to this. Only the organisations following this will keep up with the future.

Ines

Ines Garcia

Blog author

Founder at get:Agile. Empowering Agile mindset evolution (not revolution). Helping organizations to become more Agile with Scrum framework and Kanban elements while delivering Salesforce technology.

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

How To Pass Leading SAFe® 4.5 Exam ?

Scaled Agile Framework is a roadmap that leads the organizations in implementing the Lean and Agile Practices. SAFe® includes the three foundational bodies of knowledge that are System Thinking, Lean Product Development, and Agile Software Development. It helps the organizations to improve themselves according to the business requirements, deals with challenges involved in developing and delivering ideal software and systems within a specified time. SAFe® practices are essential but, sometimes they can be complex and entail some challenges. It might be easy to deal with such challenges and move your enterprise towards SAFe® practices by becoming a professional SAFe® Agilist. Passing a SAFe® Agilist Certification exam proves that you are an expert in implementing Agile and improving the project you want to get involved in.Here, in this article, we will guide you through your Leading SAFe® 4.5 exam preparation.Firstly, the 2-day Leading SAFe® 4.5 training is the most crucial part of this certification. Join the course and ask all the doubts you have during the workshop without any hesitation. Make a note of all the important things which will be helpful for future references. After completing the course successfully, you should pass the exam to obtain SAFe® Agilist Certification.Exam DetailsFormat of the examThis is a web-based, timed, and closed book exam that will be conducted in English and delivered in the format of multiple choice questions. Upon completion of the Leading SAFe® training, candidates will get access to the exam within the SAFe® Community Platform. Candidates will have 90 minutes to finish the exam once it starts.The exam consists of 45 questions in total and you must answer a minimum of 34 questions correct out of 45. You can take the exam at any time and the fee for the first attempt will be included in the course registration fee only if the exam is taken within 30 days of course completion.Retake policy of the examIf the certification exam is not cleared in the first attempt, you can retake the exam again and again, but each retake costs $50.You can take the second attempt immediately after the first attemptYou need to wait for a minimum of 10 days to retake the exam for the third timeA minimum of 30-day wait is required to retake the exam fourth timeCandidates are not allowed to retake the exam, once they got a minimum passing score of 76% unless there are updates announced to the exam.Exam preparationThe exam is specifically designed to analyze the skills and knowledge of a particular candidate. Develop a study plan before going to take the exam.Here are a few important points you should remember-You should gain both practical and theoretical knowledge in order to pass the exam successfully.The course materials are more helpful to prepare for the exam and we at KnowledgeHut offer course materials authored by the Scaled Agile Academy. These materials can be used for referring the concepts that are presented during the training.Take the practice tests that are designed with the same level of difficulty, time duration, and the same number of questions. You can take the exam without any additional cost. The practice tests once completed, let’s you know the chapters you should study more in pink color. Study those topics again.  As a preparation, on scaledagileframework.com, on the big picture (framework) click on the words if have confusion/not sure and read the guidance article. It makes you prepare well for the main certification exam and boosts your confidence level.Choosing a right path takes you to important destinations in your career. Becoming a SAFe® 4.5 Agilist is a career path for many and it requires an excellent range of skills. The best institute guides you towards a bright career. So, choose the right and best institute that is authorized to do so and can help you reach your goals.
Rated 3.5/5 based on 4 customer reviews
2450
How To Pass Leading SAFe® 4.5 Exam ?

Scaled Agile Framework is a roadmap that leads the... Read More

Scrum Master and Product Owner: Understanding the differences

 Agile methodology imparts the easy and convenient path to work. Scrum is one of the famous Agile methodologies. Agile methodologies consists of 4 main roles, viz. Product Owner, Scrum Master, Scrum team and Stakeholder. Each role has its share of responsibilities. These roles are all about commitment. Scrum master and the Product owner are two vital roles in the Scrum Software Development Methodology. Since they both are working on different areas of the project, they are indispensable for the project. Scrum Master is a mediator between the Product owner and the Development Team.       Product Owner vs Scrum Master- Though the Product Owner and the Scrum master vary in their roles, they complement each other. Scrum master should support the product Owner in every step possible. There should be an amicable relationship between the Product owner and the Scrum master. Disputes may happen between them if the roles are not clarified. Let us have a look at the differences in roles between the product owner and the scrum master. The Scrum Master concentrates on the project success, by assisting the product owner and the team in using the right process for creating a successful target and establishing the Agile principles.    Scrum Master Skills (SM): SM creates a friendly environment for the team for Agile development. SM improves the quality of the product. Certified Scrum Master Certification, adds advantage to become effective. SM protects his team from any kind of distraction and allows them to stay tuned. SM helps product owner to maximize ROI (return on investment) to meet the objectives. SM removes disputes between the product owner and the development team. SM encourages the team to meet the project deadline. SM acts like a coach for a team to perform better. A good Scrum Master should possess the skills like project management, engineering, designing, testing background and disciplines. SM provides continuous guidance to teams   Duties of Scrum Master: SM facilitates team for better vision and always tries to improve the efficiency of the teams. SM manages Scrum processes in Agile methodology. SM removes impediments for the Scrum team. SM arranges daily quick stand-up meetings to ensure proper use of processes. SM helps product owner to prepare good product backlog and sets it for the next sprint. Conducting retrospective meetings. SM organizes and facilitates the sprint planning meeting. The Product Owner’s responsibility is to focus on the product success, to build a product which works better for the users and the customers and to create a product which meets business requirements. The product owner can interact with the users and customers, stakeholders, the development team and the scrum master.   Product Owner Skills (PO): PO should have an idea about the business value of the product and the customers’ demands. Certified Scrum Product Owner Certification (CSPO) will be beneficial for the sales team. The development team consults PO, so he should always be available for them to implement the features correctly. PO should understand the program from the end-user point of view. Marketing is discussed on the sales level in most of the Organizations. So it is the PO’s duty to guide the marketing persons to achieve the goals successfully. PO is responsible for the product and the ways to flourish a business. PO has to focus for the proper production and ROI as well. PO should be able to solve the problems, completing trade-off analysis and making decisions about business deliverables. After CSPO course, PO can work with the project managers and the technical leads to prioritize the scope for product development. Sometimes PO and the Customers are same, sometimes Customers are thousands or millions of people.   Duties of the Product Owner: PO has to attend the daily sprint planning meetings. PO prioritizes the product features, so the development team can clearly understand them. PO decides the deadlines for the project. PO determines the release date and contents. PO manages and creates the product backlog for implementation, which is nothing but the prioritized backlog of user stories. PO defines user stories to the development team. Spending some time to prioritize the user stories with few team members. One can enhance his/her knowledge in many directions and beyond boundaries, after undergoing the Certified Scrum Product Owner (CSPO) training.
Rated 4.0/5 based on 1 customer reviews
2743
Scrum Master and Product Owner: Understanding the ...

 Agile methodology imparts the easy and convenien... Read More

Best ways to implement Leading SAFe 4.5 in organizations

SAFe stands for Scaled Agile Framework. This framework is mostly used by the corporate bodies which need to scale from smaller organizations to larger ones. So SAFe is also known as an enterprise-scale development methodology. This framework was coined by Dean Leffingwell. It is an ‘information base’ which is freely available, and allows you to apply Lean-Agile practices at an organization level.   Scaled Agile Framework (SAFe) is referred as the Agile framework for software development. It renders an ease of operation for the development team. SAFe 4.5 is the most updated version introduced to match the needs of the organizations. This version consists of some new features as follows:  Fastest delivery with scalable DevOps and Continuous delivery  Quick testing using the Lean Startup cycle and User Experience (UX)  Improved Portfolio performance with Lean Portfolio Management (LPM) and Lean Budgets Additionally, SAFe 4.5 allows organizations to transform from the traditional approach to Lean-Agile methodology with the new Implementation Roadmap. Implementation Roadmap of SAFe 4.5 is a guide for the organizations. Reasons to switch to SAFe 4.5: ●  The updated version of SAFe 4.5 supports the range from simplest to the most critical development environment. SAFe 4.5 is able to mould according to the organizational needs. SAFe has four new   configurations as follows:  1. Essential SAFe - an initial phase which starts just after realizing the benefits. 2. Portfolio SAFe - adds portfolio level, strategy and investment funding, guidance on Agile programs, and Lean governance as a scenario. 3. Large Solution SAFe - for building large systems that involve Agile Release Trains and Suppliers 4. Full SAFe - for the largest firms those are seeking the benefits of the Lean-Agile enterprise.   ● SAFe 4.5 works by integrating Lean Startup Cycle and Lean UX, which creates an environment to form Minimum Viable Product (MVP). It fosters quick innovation. ● SAFe 4.5 has concentrated on the feature of rapid delivery using the techniques like Scalable DevOps and Continuous Delivery Pipeline. ● SAFe 4.5 has provided a guide in the form of a 12 article series, given a name as ‘SAFe Implementation Roadmap’. Based on the Change Management technique in the organization, the roadmap       guides on the critical steps that an organization can take to achieve long term goals.  ●  SAFe 4.5 is completely backward compatible. In SAFe 4.5, you just need to adopt the advanced principles, keeping old versions in place.                                                                                                  How is SAFe 4.5 Implemented? SAFe Implementation Roadmap provides guidance to the organizations in the form of a twelve-article series which describes effective strategies and a set of activities to implement SAFe at an organizational level. Let me illustrate the 12-article series below-   Reaching the tipping point.  Train Lean-Agile change agents  Train Executives, Managers and Leaders  Create a Lean-Agile Centre of Excellence  Identify Value streams and ART’s  Create the Implementation plan  Prepare for ART Launch   Train Teams and Launch ART   Coach ART Execution   Launch More ARTs and Value Streams  Extend to the Portfolio   Sustain and Improve SAFe is a pivotal framework as it helps to achieve business benefits at an organizational level. In order to understand the outcomes of Leading SAFe implementation, organizations must embrace and understand the Lean-Agile principles. Based on the Change Management strategies in the organization, the SAFe Implementation Roadmap guides on the critical steps that an organization can follow to achieve long term goals.   
Rated 4.0/5 based on 20 customer reviews
Best ways to implement Leading SAFe 4.5 in organiz...

SAFe stands for Scaled Agile Framework. This frame... Read More