This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
People new to Scrum often struggle to understand boundaries of control between being an effective manager, ScrumMaster, or Product Owner. This is a critical consideration because, at the heart of Scrum, we’re attempting to grow a group of people into a resilient, high-performing team. Attends Daily Scrum to get a status update.
How to Be an Effective Manager in Scrum. Scrum Team Titles. Business Analyst, QualityAssurance, Software Developer, …) get in the way of working together to deliver the most value to customers. Can a QualityAssurance Lead help with Usability? Scrum Management Titles. As teams grow, job titles (e.g.
One of the more frequently asked questions in my Scrumworkshops is around the difference between Definition of “Done” and Acceptance Criteria , and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of “Done” is unique to Scrum. User Stories.
How long should a Scrum Sprint be? A Scrum Sprint is a short period of time when the Scrum Team works, but there is no hard rule as to how long that should be – in this post, we cover the pros and cons of shorter and longer Sprints and how you can discover what works best for you. This leads to the dark side and Scrum Theatre.
One of the more frequently asked questions in my Scrumworkshops is around the difference between Definition of “Done” and Acceptance Criteria, and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of “Done” is unique to Scrum.
There are two major ways to discover opportunities for cross-skilling: Kanban/Scrum Team Board. Kanban/Scrum Team Board. QualityAssurance or Editing) is so effective. Skills Matrices and Scrum/Kanban Team Boards will only get you to the point where you know there is a need for growth, and where. Skills Matrix.
A Scrum Sprint is incomplete when the Team can’t deliver the working features they committed to. Tonia – the Team’s QualityAssurance specialist. Tonia (QualityAssurance specialist), spends the first few days working with Brad (Business Analyst). We cover the reasons for this and how you can help your Team.
Before release, the software product undergoes strict quality control procedures to eliminate flaws, ensure its effectiveness and performance. You can read our article about the basics of software quality management to better understand the principles of qualityassurance, quality control, and testing.
Is your Scrum team struggling with questions about who owns quality? Let’s use our fictional World’s Smallest Online Bookstore (WSOBS) Scrum team to explore what this Scrum anti-pattern is and the damage is causes. Isn’t Scrum about giving us autonomy and getting stuff done? Is testing way behind development?
Tonia – the Team’s QualityAssurance specialist. Doug was late for Daily Scrum on several days. When that happens, people opt to stay silent when there is an opportunity to share an opinion, and events like Daily Scrum becomes less useful when Team members signal their disrespect by frequently being late.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content