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
The Bad Apple Effect can deeply sabotage a teams performance and development. Even with talented, capable players, their respective teams often underperformed and struggled to progress in their development. Still, these negative attitudes were affecting the whole team's morale and teamwork.
He says, Before complaining that Agile/Scrum/whatever is dead, consider instead that it's become a norm. Teams are not evolving beyond the laid out frameworks or methods. In my experience, I have seen the frameworks, methods become practices to be followed only to showcase a client that the team is doing agile.
As we ease into the new year, many organizations’ executive teams are ramping up hiring for new talent. All these efforts require precise judgment to hire just-in-time talent, using data to make strategic project decisions at a portfolio, program and project level and launching new high performing teams.
For example, take scrum. Scrum is a great framework for helping teams work more productively together. In fact, the name comes from rugby and like it, scrum is a team sport. Teams learn through experience, reflective meetings and specific roles that add structure and manage work. Scrumban: An Agile Hybrid.
An effective Sprint Retrospective ensures the team remains cohesive and aligned, leading to sustainable development and innovation. Still, the decision to skip a single Sprint Retrospective can adversely affect the team and the product's development process. With this reflection, teams can iterate on their process.
As many scrum masters set out on their journey, they are often as new to their role as their manager. This post (inspired by Ben Horowitz author of “The hard things about hard things”) is for scrum masters, and people who work with scrum masters, and explores what good and bad looks like.
TL; DR: DevelopmentTeam Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses DevelopmentTeam anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the DevelopmentTeam in Scrum.
In the past years, Johannes Schartau, Christiaan Verwijs, and I wrote many articles on Zombie Scrum. Heck, we even wrote a complete Zombie Scrum Survival Guide ! I’d like to believe that since our book, Zombie Scrum completely disappeared. But Zombie Scrum is still present in different shapes and forms. Zombie Scrum?
The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software developmentteams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition.
No wonder project teams look for open-source Microsoft Project alternatives. Because Microsoft Project can be such a pain to use, project managers and their teams seek alternatives. The more technical teams, working in IT and other departments, are familiar with open source and the Linux operating system.
The ScrumTeam delivers a valuable, useful, and usable Increment(s) every Sprint. In my view: It could be a "layer of cake team", in that it cannot in and of itself delivery value without dependencies on other "layers" of the cake. ScrumTeam members strive for net improvements. Self-managing.
In Scrum, the Sprint Goal serves as the spotlight that provides transparency to the Sprint Backlog, as the flag that allows the team to rally, and the one thing that provides focus and cohesion. The following nine Sprint Goal principles point at critical issues any Scrumteam needs to consider on its path to excellence. ????
Scrum was introduced in 1995. Since then, as more people, teams, and organizations have started using Scrum, the framework has grown into the most used method for agile product delivery. And as the popularity of Scrum started to grow, many misinterpretations of the framework grew with it. The power of Scrum.
Does your team struggle to get items to Done? Do they experience a high amount of spill-over into the next cycle because they are waiting on another team or another person? Do items sit in a blocked state and age out while waiting on other teams or people to complete work? Dependencies are an epidemic in software development.
TL;DR: The Alignment-to-Value Pipeline Effective product development requires both strategic alignment and healthy Product Backlog management. By implementing proper alignment tools, separating discovery from delivery, and maintaining appropriate backlog size (3-6 sprints), teams can build products that truly matter.
If product owners fail to maximise the value produced by the team, the entire product development can be derailed. Failing to understand and validate value leads to the team missing the intended goals. The Product Owner must maximise the value the team can deliver.
Of late, I've been noticing an interpretation of the Scrum Master role - the Scrum Master as An FFFCDO for Developers - a Fierce, Ferocious, Fearsome Chief Defense Officer! What is the Scrum Master protecting the Developers from? Who are the persecutors the Scrum Master protecting the Developers from?
Scope creep is the more common term but you might hear both, especially if you are working in software development. Ultimately, it isn’t the project manager coming up with new requirements and asking the team to “just do it”. What’s so bad about scope creep anyway? It takes its toll on team morale.
Suitable agile metrics reflect either a team’s progress in becoming agile or your organization’s progress in becoming a learning organization. At the team level, qualitative agile metrics often work better than quantitative metrics. A team may have deliberately built some temporary solutions to speed up experimentation.
The secret to scrum is simplicity, even in the face of complexity. And although scrum is simple at heart, it can be difficult to master. Scrum requires self-organizing teams that can quickly solve problems in unpredictable environments. Scrum ceremonies are meetings that are unique to scrumteams.
Implementing Test-Driven Development (TDD) enhances readability, maintainability, and modularity. Even AI exhibits caution in refactoring without tests, mirroring human developer behaviour. Would it resemble code developed using TDD principles? TDD vs. AI: Is AI Truly Applying Test-Driven Development?
The lecture triggered many thoughts about the relevance of teaching Agile/Scrum. The first paper was a 2012 study on the tensions with remote (off-shoring) teams (Ramesh et al Ambidexterity in Agile Development ISR2012). It confirmed my preconception that regular education struggles to keep up with developments in our field.
Some time ago, someone on Reddit asked whether there would be any other profession that requires attending a 2-day training class and would then pay as well as a Scrum Master job. This attitude is precisely why the 47 Scrum Master Interview Guide exists: Prevent imposters from slipping through the hiring process and causing damage.
TL; DR: 20 Questions a New Scrum Master Should Ask. Twenty questions for you — the new Scrum Master — that fit into a 60 minutes time-box. Start learning how your new ScrumTeam is currently delivering the product and get up to speed: from Product Backlog forensics to metrics to team challenges and technical debt.
Long has spoonfeeding solutions and off-the-shelf feature descriptions prevailed in many developmentteams. Although some issues might have been fixed, I rarely see the full potential of a ScrumTeam being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.
According to the Scrum guide, Scrumteams typically have 10 or fewer people, including Developers, Scrum Master and Product Owner. But what happens with a Scrumteam that includes more than 10 people? What if the Scrumteam has 10, 15 even more people? Some people check out. .
. Can scrum be used outside software development? I’ve often worked in cases in non-software where I might have had 10 options that I would consider for the team. If you understand more about the business domain and the technical domain, you understand what the team is doing. Absolutely. .
During the first year of the pandemic, Scrum adoption more than doubled for software developmentteams. According to the 15th Annual State of Agile Report, the use of agile approaches for software development grew from 37% in 2020 to 86% in 2021. It is, in essence, the plan for what the ScrumTeam will do next.
Scrum is simple, but that simplicity means that each of its elements is essential. Teams that mess with the framework are messing with Scrum. Teams that make changes to the elements limit Scrum's effectiveness and aren't really using Scrum. . The team struggled to deliver a Done Increment each Sprint. .
Every ScrumTeam, at some point, will struggle with how to facilitate the Daily Scrum. It's the Daily Scrum, not the "stand-up.". It's a collaborative working session where the Developers on a ScrumTeam update their work and plan to progress towards their Sprint Goal over the next 24 hours.
However, a ScrumTeam may not always have a Valuable Product Owner. The Product Owner Proxy or Proxy Product Owner: In my past article about practices leading to anti-patterns I mentioned the Proxy Product Owner being a widely used practice, especially in scenarios where you have distributed teams or onshore-offshore models.
TL; DR: ScrumDeveloper Anti-Patterns. After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses ScrumDeveloper anti-patterns, covering all Scrum Events and the Product Backlog artifact. The Role of the Developers in Scrum.
A Scrum Event is a meeting. Given the poor reputation that meetings have, maybe it's not a surprise. Rather than replicate the name and pain of meetings, the Scrum Events are designed to replace them and be all that you need. The power of the Scrum Events is in the way they're time-boxed and in their purpose. Daily Scrum.
Managing marketing projects comes with unique challenges—from balancing creative workflows and aligning teams to meeting tight deadlines and handling last-minute changes. In this article, we’ll explore the 10 best project management tips specifically tailored for marketing teams.
In this article you will learn: Why enabling ScrumTeams with UX Design capabilities is important. Why introducing UX capabilities to Scrumteam is frequently hard. What is the job of an UX Leader in a product development organization. The narrative around Scrum is centered on delivering products.
I’ve been part of the Scrum community for about 12 years. In this period, I’ve noticed a clear pattern in the majority of Scrum-related threads on social media like LinkedIn, Medium, Twitter, and so on. As a community, we excel at putting our fingers on the sore spots of what teams and organizations do wrong.
TL; DR: 70 Scrum Master Theses. The following 70 Scrum Master theses describe the role of from a holistic product creation perspective. The theses cover the role of the Scrum Master from product discovery to product delivery in hands-on practical manner. The Role of the Scrum Master. It is not a mere management role.
TL; DR: Scrum Master Interview Questions on Scrum Anti-Patterns. Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world , a seasoned Scrum Master is nowadays in high demand. Which makes any Scrum Master interview a challenging task.
From the Scrum Guide: The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. In Scrum a commitment is always towards a goal, never towards busy work. Why do most ScrumTeams struggle with it?
Long has spoon-feeding solutions and off-the-shelf feature descriptions prevailed in many developmentteams. Although some issues might have been fixed, I rarely see the full potential of a ScrumTeam being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.
TL; DR: Scrum Stakeholder Anti-Patterns. Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition. Do you want to get this article in your inbox?
TL; DR: Scrum 2022 — Getting You Started as Scrum Master or Product Owner. Probably, you are considering how to further your Scrum Master career or Product Owner career in 2022. Good luck with Scrum 2022—just stick to first principles! Join Stefan in one of his upcoming Professional Scrum training classes !
According to the 2020 Scrum Guide, Scrumteams are “self-managing, meaning they internally decide who does what, when, and how.” The most empowered Scrumteams in my experience not only decide who does what, when and how, they also control the structure and organization of the Scrumteam itself. .
Part of the Scrum Master accountability is finding effective tools for Product Backlog management, which often means that the Scrum Master is accountable for setting up the Scrum Board. There are many ways to create a Scrum board. There are many popular software applications which can be used to create a Scrum board.
We organize all of the trending information in your field so you don't have to. Join 100,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