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
Frequently in workshops, I get asked, “Where shouldn’t we use Scrum?” The short answer is there are lots of instances where the Scrum framework doesn’t fit. However, to give a more complete and effective answer to this question, first we need to have an idea of why and when Scrum does work and what the key conditions are for success.
2+ years of backend development experience. Experience in ContinuousIntegration. Agile Methodologies: Scrum ( Jira ). Experience in TestDrivenDevelopment and unit testing. Spanish native or bilingual. Experience with some of the following languages: PHP, Kotlin, Node.js. DevOps experience.
This is a transcript of my keynote presentation for the Regional Scrum Gathering Tokyo conference on January 8th, 2025. They also love test-drivendevelopment, pairing, continuousintegration, and evolutionary design. They tend to be passionate, senior developers. How are you measuring productivity?
And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Most scrum masters don’t take these points into consideration while planning their sprints. new bugs can occur at any point in time. And value is what you’ll receive?—?but
And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Most scrum teams don’t take these points into consideration while planning their sprints. Trust me — new bugs can occur at any point in time.
And with no set approach in place, software development teams often find themselves in a never-ending bug chase, which is another reason behind delayed releases. Most scrum teams don’t take these points into consideration while planning their sprints. Trust me — new bugs can occur at any point in time.
LeSS, which stands for “Large-Scale Scrum,” is one of the original Agile scaling approaches. Despite the name, it’s not a pure Scrum-based approach. Then each team works independently on the priorities they chose, using continuousintegration to keep all teams’ work in sync. Test-DrivenDevelopment.
Hi, I’m your Scrum Master,” she says. Until then, development on an Agile team looks similar to development on any other team. TestDrivenDevelopment. They use test-drivendevelopment to write tests, implement code, refactor, and incrementally design and architect the software.
This can be achieved using methodologies like Scrum, Kanban, SAFe®, DevOps etc, leading to responsive business prioritization and short delivery iterations. Of course, this also demands a rethink of your operational model with vendors and major partners.
One of the things Scrum has contributed to the practice of software development is the idea that small autonomous teams perform much better than large project teams or single-discipline teams that work in sequence.
A programmer makes an off-by-one error, but their pairing partner suggests a test to catch it. A team member accidentally erases a file, but continuousintegration rejects the commit. Searching for a “single, wringable neck,” in the misguided parlance of Scrum, just encourages deflection and finger-pointing.
To counter sequential processes and the long integration and defect removal phase, agile software development practices focused on fast feedback cycles in these areas: Test-drivendevelopment: Start by writing tests (think of them as executable specifications) and then write the code to pass the tests.
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