Search

Check Out The 5 New Scrum Values Added To The Scrum Guide

The original Scrum Guide was based on the three pillars of Scrum—Transparency, Inspection and Adaptation. These pillars ensured the team adapted to changes, and respected each other thereby creating a fun yet focussed work environment. It wasn’t until the 23rd of October, 2014, that the five Scrum Values were added to the Guide, upon suggestion by Iain McKenna. Let’s delve a little deeper into what these Scrum Values, commonly called C FOR C, are. 1. Commitment This value can be taken up in three aspects. Sprint-based commitment: Sprint is designed to reflect realistic goals in a short duration of time. The team has to be committed to working towards meeting this goal. Commitment as a team: As a team, you have to welcome changes and depict adaptability. You’ll also have to gain value while accomplishing small yet concrete goals in a step-by-step manner. Through a collective decision, the team has to work and achieve the predetermined goals. Also, if there is any urgency in accomplishing the task, the team can discuss and come up with an effective solution while also maintaining harmony. Commitment as an individual: Being able to contribute as much as possible to your team and towards the sprint goal shows your commitment as an individual. Commitment towards learning, collaboration, scrum values, working software, and team requirements are some of the ways you can do your bit. 2. Focus Once your goals are defined, the most basic way to achieve them is to be goal-oriented. This not only motivates you to be faster and better, but also helps in maintaining harmony in the team. By focussing on working towards the target, you tend to waste less resources and time. With the help of the Scrum Master and Product Manager, you can evade external interferences to ensure there are no hindrances to your workflow. In Scrum, you deal with several short-term goals to eventually provide product shipping. At the end of each sprint, you will be able to set new goals and provide more flexibility and adaptability to project needs. With Scrum, you have the benefit of a lower rate of risk and ample time to correct issues and complete targets. 3. Openness As already mentioned, every individual in a team has to make a contribution towards achieving goals in a project. So you, as an individual, have the freedom to express your perspective and any contributions to the project. This level of transparency gives a clear picture of the status of the project, any probable challenges the team has to gear up for, and the orientation of the project to not just the team members, but also to the ScrumMaster and the Product Owner. The team is open to appreciation as well as criticism. You can discuss the possibilities of improving the project as well as share any information that you think is necessary to be put across to your team or managers. You never know when a brilliant idea might be pitched which could change the entire course of the project. 4. Respect Any work environment where colleagues respect, care for, and appreciate each other provides a positive vibe and encourages individuals to be efficient. With this value, Scrum ensures that irrespective of your background and experiences, the team is always going to support you. This quality is inter-related to openness, as people can express their thoughts and ideas only when they know that appreciation and encouragement is in store. With respect, the team has no room to blame or complain about each other, but in turn provide motivation amongst themselves. 5. Courage Adaptability to change is the base of any Scrum project. To embrace change requires courage. The team is allowed to experiment with different approaches to the situation and the issue to identify the best and most suitable solution. In order to provide unique and new solutions to the team, courage is essential to come out with your ideas in front of the team. Scrum is all about taking risks and finding innovative solutions. It also takes courage to question conventional decision making methods. With the adaptation of the five values in your projects, you also eventually tailor your team to follow the Scrum pillars. With the commitment to these values, there is harmony maintained in the team and they work together to create unique ideas for improved results. With the Scum pillars as the base and Scrum Values adding to it, the team can provide exemplary results in minimal time while acknowledging the excellence of Scrum in their work.
Rated 4.0/5 based on 20 customer reviews
Check Out The 5 New Scrum Values Added To The Scrum Guide 520
Check Out The 5 New Scrum Values Added To The Scrum Guide

The original Scrum Guide was based on the three pillars of Scrum—Transparency, Inspection and Adaptation. These pillars ensured the team adapted to changes, and respected each other thereby creating a fun yet focussed work environment.
It wasn’t until the 23rd of October, 2014, that the five Scrum Values were added to the Guide, upon suggestion by Iain McKenna. Let’s delve a little deeper into what these Scrum Values, commonly called C FOR C, are.

1. Commitment

This value can be taken up in three aspects.

Sprint-based commitment: Sprint is designed to reflect realistic goals in a short duration of time. The team has to be committed to working towards meeting this goal.

Commitment as a team: As a team, you have to welcome changes and depict adaptability. You’ll also have to gain value while accomplishing small yet concrete goals in a step-by-step manner. Through a collective decision, the team has to work and achieve the predetermined goals. Also, if there is any urgency in accomplishing the task, the team can discuss and come up with an effective solution while also maintaining harmony.

Commitment as an individual: Being able to contribute as much as possible to your team and towards the sprint goal shows your commitment as an individual. Commitment towards learning, collaboration, scrum values, working software, and team requirements are some of the ways you can do your bit.

2. Focus

Once your goals are defined, the most basic way to achieve them is to be goal-oriented. This not only motivates you to be faster and better, but also helps in maintaining harmony in the team. By focussing on working towards the target, you tend to waste less resources and time.

With the help of the Scrum Master and Product Manager, you can evade external interferences to ensure there are no hindrances to your workflow.

In Scrum, you deal with several short-term goals to eventually provide product shipping. At the end of each sprint, you will be able to set new goals and provide more flexibility and adaptability to project needs. With Scrum, you have the benefit of a lower rate of risk and ample time to correct issues and complete targets.

3. Openness

As already mentioned, every individual in a team has to make a contribution towards achieving goals in a project. So you, as an individual, have the freedom to express your perspective and any contributions to the project.

This level of transparency gives a clear picture of the status of the project, any probable challenges the team has to gear up for, and the orientation of the project to not just the team members, but also to the ScrumMaster and the Product Owner.

The team is open to appreciation as well as criticism. You can discuss the possibilities of improving the project as well as share any information that you think is necessary to be put across to your team or managers. You never know when a brilliant idea might be pitched which could change the entire course of the project.

4. Respect

Any work environment where colleagues respect, care for, and appreciate each other provides a positive vibe and encourages individuals to be efficient. With this value, Scrum ensures that irrespective of your background and experiences, the team is always going to support you.

This quality is inter-related to openness, as people can express their thoughts and ideas only when they know that appreciation and encouragement is in store. With respect, the team has no room to blame or complain about each other, but in turn provide motivation amongst themselves.

5. Courage

Adaptability to change is the base of any Scrum project. To embrace change requires courage.

The team is allowed to experiment with different approaches to the situation and the issue to identify the best and most suitable solution. In order to provide unique and new solutions to the team, courage is essential to come out with your ideas in front of the team.

Scrum is all about taking risks and finding innovative solutions. It also takes courage to question conventional decision making methods.

With the adaptation of the five values in your projects, you also eventually tailor your team to follow the Scrum pillars. With the commitment to these values, there is harmony maintained in the team and they work together to create unique ideas for improved results.

With the Scum pillars as the base and Scrum Values adding to it, the team can provide exemplary results in minimal time while acknowledging the excellence of Scrum in their work.

KnowledgeHut

KnowledgeHut Editor

Author

KnowledgeHut is a fast growing Management Consulting and Training firm that is a source of Intelligent Information support for businesses and professionals across the globe.


Website : http://www.knowledgehut.com/

Leave a Reply

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

Suggested Blogs

Agile Scrum Roles And Responsibilities

Agile, Scrum, Waterfall, Kanban are different project management frameworks which are helping the companies to increase the productivity. These frameworks were created by the IT companies and especially web and application development companies because they needed a path but on which each and every employee can perform his daily tasks. However, out of these four frameworks, the Scrum is the most widely used framework in all the companies despite their nature of work. That is why in this article we are going to discuss the Scrum in detail to give you a better idea about this iterative framework which is making easier for the companies to complete their project. Scrum Objective: The basic objective of the Scrum is to keep the entire team on the same page throughout the project. The scrum framework allows the cross-functional work of the team of 4 to 10 members to provide the regular details and information sharing liberty so they can produce the best result. Scrum is a more like philosophical than the technical. It is a framework that can only be used as the guidance and there is no constant in it. All the success of the Scrum depends on the interactions among the stakeholders as it does the process. Scrum roles and responsibilities: The techniques of Scrum has become very popular and now considered to be the most important thing to do before starting any project. That is why the demand of the scrum masters and other professions related to the scrum has also increased, and people now are searching about the term scrum more. The scrum is a very specific and précised framework that is why it comprised on the following roles. Scrum Master Product Owner Scrum Team Stakeholders Because the term Agile is often get associated with the project managers that is why many people believe that the Scrum Master is also a term for the project managers. However, the Scrum Master serves very different purposes than the project manager. The Scrum Master works as a facilitator rather than the authoritative person who is responsible for the project delivery. The Scrum Master is a coach, motivator and problem solver who can only assist the team by using all his experience of Scrum framework. According to many Scrum Masters, applying Scrum within an organization is not the actual scrum process. You have to make the organization to accept your new role and then change its culture which is the most difficult thing to do in any company. The prominent role of every Scrum Master should be to enhance the power of the team by committing them to the sprint goals without any interference from the management. Let’s discuss the major roles of all the above points separately. Scrum Master: The Scrum Master is considered to be the top-dog in every organization because companies usually hire them and don’t treat them as permanent employ that is why they are with no authority. It is their duty to remove all the hindrance or obstruction in the way of achieving any goal. It is also their role to enforce scrum ceremonies and processes. They are the ones who commit to goals and deadlines on behalf of the team. Product Owner: The product owner is responsible for conveying the vision of the stakeholders to the team. They have the authority to alter the scope. The Product Owners are responsible for the return on investment (ROI) that is why they occupy an authoritative position in the firm. Because they convey the vision of the stakeholders that is why they are the voice of the stakeholders. Not only with the team, but they also communicate with the stakeholders about progress and problems. Scrum Team: The Scrum Team is responsible for all the activities that lead them towards their sprint goals. They have to work with the Scrum Master to prioritize the items from the product backlog in the sprint planning. Once committed, it is their responsibility to fulfil the commitment and deliver the agreed results on time with great quality. The Scrum Master is not responsible for keeping his team organized that is they it is the duty of the Scrum Team to get self-organized. They have to be agile in the office and have to attend every standup and other ceremonies. They have to participate in all the meetings despite their nature and have to ensure that all the findings of the meetings are getting practically addressed in the project. Stakeholders: The Stakeholder has to keep a healthy relationship with the Product Owner in order to share every detail regarding his project. The Stakeholder is responsible for conveying his wishes and concerns to the product owner or else the product owner would not be responsible for his project quality and time duration. The Stakeholder has to provide regular input to queries from the Product Owner. Prioritizing the work affectively with the Product Owner is another job that the Stakeholder has to do to ensure his project development. Keep taking updates or keep giving updates regarding any change in the plans.
Rated 4.0/5 based on 20 customer reviews
Agile Scrum Roles And Responsibilities

Agile, Scrum, Waterfall, Kanban are different project management frame... Read More

CSM, PSM, SSM, SASM - What Scrum Master Course Do I Choose?

Scrum adoption is growing very fast and companies are looking for well qualified Scrum Masters. This is one of the main reasons to consider Scrum certification. One simple way to present your excellence is the Scrum Master certification that is perfectly tailored to the industry requirements, and of course, to your career trajectory. Currently, there are 4 primary Scrum Master certifications available. You might be in a confusion regarding the best course to take up for a superior career growth.  Question yourself on some of the essentials before actually choosing the course:  What does the particular certification mean? What are the prerequisites for this certification? What is the cost of this certification program? What will I achieve by taking this certification? Will this certification offer the biggest benefit for me?  In this article, we will help you in choosing the best certification that suits your profile by comparing all the courses based on different aspects.  CSM, PSM, SSM, SASM - What Scrum Master Course Do I Choose? https://t.co/hRgUIZfV1Z — विवेक कृष्णान (@vksvicky) May 17, 2017 All the 4 certifications are competing equally in the Scrum world. The above certification comparison demonstrates multiple facets of the in-demand Scrum certifications. Experts need to choose the course wisely based on their targets. For example, the target can be whether to: Get benefits in their job change or career or Reach greater heights in Scrum role by gaining in-depth knowledge Just choosing the right course is not enough for a better career growth, but choosing the right training provider will have a great impact on the success of a course. KnowledgeHut as a Global Registered Education Provider (REP) of Scrum Alliance offers the best training from Certified Scrum Trainers approved by Scrum Alliance. All the best for your future Scrum endeavours!  
Rated 4.5/5 based on 4 customer reviews
CSM, PSM, SSM, SASM - What Scrum Master Course Do ...

Scrum adoption is growing very fast and companies are looking for well... Read More

New Ideas For Scrum Master Day To Day Activities

Large swathes of IT organizations are embracing Agile. This is both a good and bad news. Good news, for the many boons of Agile and Scrum known to all. Bad news, because you are no longer enjoying the benefits alone. Every day, every hour, more number of functional IT teams are making Agile work for them. Each in their own unique ways.  So what is the only way to not lag behind in the Agile race?                                                                                                         Always welcoming brand new ideas! Just like always, the beginning has to be done with the mainstay of the Agile team- The Scrum Master! If you are aware of the daily life of a Scrum Master, you already have the best of Agile cards to lay your hands on. The first and the best card is to relook and rethink the daily activities of a Scrum Master. Crossing this milestone will give you an idea of a few new entries in the existing Scrum Master’s checklist.  The Scrum team consists of three roles- Product Owner, Scrum Master, and Team members. Everyone thinks that a team member who develops the software all day and a Product Owner who shapes the product all day, have full-time jobs. But based on assumptions, being a Scrum Master does not always mean having a full-time job. In any case, the role of the Scrum Master is highly important, as he/she manages the Scrum operations of the entire team.  "A Day in the Life of a Scrum Master" https://t.co/IVoiKxEAfF by @Barryovereem on @LinkedIn — Jacek Durlik (@jacek_durlik) September 4, 2017   Let us take a look at a day in the life of a Scrum Master:   Start the day with a ‘free and open mind’ Can ask a good question like “How can I facilitate creativity for the Scrum team to improve their lives?” Attend the Daily Scrum as a facilitator- You just need to listen to what things are being discussed in the meeting by team members. Consider some of the questions that are mentioned earlier. Based on the surveillance, you execute your next step. This might be coaching, facilitating, managing, problem-solving, conflict resolving, etc.  Getting too busy and not noticing the concerned things is an activity which should not happen to a Scrum Master. The above-mentioned tasks should be the Scrum Master’s daily checklist. Collated below are some new ideas for Scrum Master day to day activities that can help improve your Agile practices.  1) Play dual roles: Scrum team members should always keep changing their area of expertise. Sometimes they should be able to choose a work which is outside their comfort zone.  For example- If you are a User Interface developer (where you know all the secrets of the domain) then you can try to work on the data access code too.  How to implement- Let us go with the above example. To enforce data access code, more than one team member has to work on a user story. Secondly, confine the user stories which are under ‘task in progress’, that is one user story should be smaller than the team size. Also, it can be implemented performing pair programming.     Takeaways-   Enforcing the thing which is out-of-the-box can help expand your knowledge. More people will come to know about all the aspects of the software (how a software works, what are the resources needed, etc.). This will increase the courage of the team member. The courage to venture beyond their boundaries. They can gradually perform tasks that are outside their expertise, lowering risks of failure, and enhancing team spirit.  2. Ask to check commit review: Whenever a developer writes code and wants to check-in that code, test, and document to the version control system, he/she asks a co-developer to review the changes first. The developer can implement this by adding ‘commit reviews’ to the ‘definition of done’. Also, they can refuse the user stories for which commit reviews are not mentioned (can be viewed as a version control system). Takeaways- At least one person has been aware of the changes, this means he/she may continue working on this particular topic if the situation demands. It increases ‘know-how transfer’. It will help increase the overall quality, as the peer developer can challenge the decision made by the prior developer. This leads to better and painless solutions. The original developer will go through the changes and explain them to this peer, which will definitely help both enhance their knowledge and skills. It increases understandability to reply to the queries of the peer developer. 3. Give awards and celebrate the victory:   Being a Scrum Master, you can introduce the culture of celebrating a victory. For example- you may give little presents to the team (whole team, not only for the individuals) for achieving a Sprint goal. This will increase the motivation of the whole team.  4. Managing test-driven development: You can introduce test-driven development for developing the software.   Takeaways- A team can work in parallel with the use of mock objects, with no need to wait for the availability of real dependencies. A team can refactor the code to initiate new functionality without changing the already existed functionality. Defect count will get reduced due to the double check done by the developers.  5. Arrange workshops on coding guidelines, designs, tools and different engineering practices: Arrange workshop for the team members where you can discuss or try a new tool, current architecture, latest technology, build process and many more. This can be implemented by reserving time for the workshop and organizing an arbitrator (can be from the team).   Takeaways- Built team spirit, where a team can perform their own way. All team members will commence working in a team way rather than individual way, which will enhance team-wide consistency. Team can stay committed to each topic. 6. Coding DOJOS: In a Coding Dojo, the entire team gathers together in a discussion room. Two developers from the team perform pair programming at a computer which is connected to a projector for other team members. The pair is whirled every 15 minutes. In this way, team solves each other’s queries to develop engineering skills. This can be implemented by reserving time for the event (coding Dojo) and arranging a moderator.   Takeaways- The team will get an idea about how to develop a software. Know-how transfer can be achieved on all topics related to software creation.  7. Testing day:   When there is a lack of testers in the team, you can introduce ‘Testing day’ in the organization. Let each team member test the application and as a compensation for that work, that team member is freed from all coding tasks.   Takeaways-     Complete focus will be on testing. No task switching is allowed to get more efficient testing output and increased quality. As entire team participates in testing, they can share individual responsibility for the quality.   8. Urgent call for Scrum meeting:   Involve team members whenever there is an emergency to mitigate the risks which are inhibiting the Sprint goal. In that case, all the team members have to drop the current task and join the meeting.   Takeaways-   Big errors can be taken care of quickly. All the team members will get convinced that they are not alone. 9. Introduce WIP (Work-In-Progress) Limits on the Scrum Board:   When there forms a stack of the user stories on the Scrum Board, you can put forward WIP limits on the boards. These limits will compel you to take care of the user stories that might block a flow. E.g. Developers may assist the testers by writing automated tests on the scenarios that have to be tested. This can be enforced by-   Writing the limits on the Scrum board Calling an emergency Scrum meeting whenever a limit is violated  Takeaway-   The status of more user stories will be ‘done’, removing them from the ‘to-be-done tasks’ list.   10. Kanban Scrum hybrid: Rate the team capacity (in %) for working on user stories. So the PO can make use of this rating for the unplanned items that need to be finished early without delaying or canceling a Sprint. Once the current task is over, team members are compelled to take an item from the fast-lane (till the reserved time is utilized), before working on the regular Sprint backlog items. If the reserved time is not sufficient to end the backlog items, then the PO can either wait for the next sprint or cancel the sprint.    FYI- Kanban is a tool which organizes work efficiently. This tool breaks work to a small chunks and uses a Kanban Board (similar to Scrum Board) to represent the progress of the work.     Takeaways-   Can earn benefits from the Sprint planning and release planning. The team can stay focused on a Sprint goal. 11. Manage time boxes of Spikes: Make sure that the time boxes set for Spikes are taken care by the team members. Also, ensure that the user stories are prioritized. Try to show the results to the team members during each retrospective.   Takeaways-  Transparency in the team’s work. If the user stories are prioritized then it will not only maximize the value of the product at the end of each Sprint but also minimize a list of the pending tasks. Following the time-boxes not only helps in planning the future spikes but also holding a Sprint goal.    12. Fixing bugs before working on user story task:   Initially, all the team members need to fix the bugs before working on a user story.   Takeaways-  Bugs are not piled up on the Scrum Board.   Motivation will be high. Quality will be better if the defects are zero.  13. Vertical User stories + Specialist → Pair Programming:   While working on a user story, if one domain expert shares his/her knowledge with another domain expert, then the knowledge transfer can be easy to the other team members. The user stories and specialist forms pair programming. At the Scrum meeting, you can decide the pairs and their respective tasks.    Takeaways-  Knowledge can be transferred from the specialist of the team. The whole user story can be implemented consistently due to the pair programming concept. 14. Personal Sprint goals:   Every team member selects personal Sprint goals, once the retrospective is over. Typically, personal goals are related to the improvement in the engineering skills or new tools. Achieving these goals makes the team members more efficient. Some of the primary goals are-  Learning Visual Studio Learning Resharper tool Providing good method/variable/tests, for each Sprint Preparing small methods, for each Sprint Takeaways-   Every team member can learn something from each small Sprint also. Increased motivation of the team members.   15. Know the difference between Spikes and User Stories:   You should always remember that Spikes have a fix time-box and an estimated result, whereas, User stories have a fixed result and an estimated time. So you can use User stories when you know what you want and Spikes when you want to plan the unknown.   Takeaways-  Spikes allow you to plan a Sprint. Work hours will not be wasted. Better focus due to fixing functionalities It allows more disciplined manner of working (i.e team members can either get the functionality fast or get an information within the defined time limit).  Do’s and Don’ts for the Scrum Master-   Concluding Thoughts-   The role of the Scrum Master is still shrouded in a mystery.  It is said that the Scrum Masters are the voice of the Scrum framework at the team level. Scrum is indeed all about continuous improvement and learning. It is also about adding new hacks to the working culture. When it comes to Agile and Scrum, you definitely cannot achieve everything overnight. All you need is to get laser-focused on the newly incorporated Scrum practices and think of innovative ways to spearhead your team to greater altitudes.  It’s time to get started with the new!   
Rated 4.5/5 based on 2 customer reviews
New Ideas For Scrum Master Day To Day Activities

Large swathes of IT organizations are embracing Agile. This is both a ... Read More