Scrum isn't about getting work done faster. It's about learning where a development team needs improvement - then delivering the right thing to customers. Scrum is a selection of agile development practices that are only a subset of what's needed for companies to have business agility. Ken Schwaber popularized its use on teams in the 1990s. Many teams that say they are "doing agile" on a software project are actually using the Scrum development methodology. In it, teams do the work needed to complete a software project in iterations, also known as sprints. Each sprint has activities similar to waterfall projects, with the addition of meetings at the beginning (the sprint kickoff) and end (the sprint review) that scope and show off the work respectively. Additionally, scrum introduces the concept of a ScrumMaster, a role someone on the team takes to remove blockages the team runs into. The ScrumMaster is also the chief evangelist of the process. In many companies, someone with a Product Management or Product Owner role take on this role, unfortunately without enough training in Scrum to have expertise in the process. Due to this, some teams rotate assignment of the ScrumMaster where each member of the delivery team takes turns each sprint playing this role.
All Content about Scrum
Many software development teams use an agile backlog but have NO business agility – and are actually using scrum with a waterfall mindset!
What is it about scrum that’s made programmers hate coding so much, and how can you prevent this on your software development team?
In working with many teams and companies, when developers are frustrated on their agile project – it’s often forecasting that’s the culprit.
Blame-shifting and improper application of scrum got people fired on a software project I was on where the client was inexperienced with agile.
Let me help you avoid some bad advice I see out there about what user stories are and how they can help (or hurt) you.
Ever been on a software development project where one team is putting pressure on another because of a hidden agenda? I was, and things got interesting…
When talking about the differences between scrum (or kanban) and agile development, the motor and steering wheel of a car can be a useful analogy.
It’s always been popular to tell people how they’re “doing it wrong” and agile software development is just as easy to call “fake”.
Let me tell you a story about one of the weirder software projects I’ve been on – and how trying to change the culture went wrong.
Does it ever feel like the daily scrum meeting is really just another status meeting in disguise? Get help in this episode of healthy software developer!
In working with over 30 companies, I’ve seen 7 common agile software development fails that have little to do with whether you’re using scrum or kanban.
Planning poker might be just what your team needs – but depending on the culture it can also cause big problems.
Too many companies and agile coaches keep the secret of scrum from people! Without understanding WHY to use scrum – misery often results.
A team that learns from software project failure produces better software – when you plan to exploit this ability.
Cross functional teams get people with different disciplines to work together better when developing software.
Embarking on the journey to let customers lead YOU to the most profitable solutions? You’ll probably need to decide between the two most popular ways agile teams work, and I’m here to help you make that decision.