Scrum.org - The home of Scrum. ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum.
Every Scrum role, rule, and timebox is designed to provide the desired benefits and address predictable recurring problems. ScrumButs mean that Scrum has exposed a dysfunction that is contributing to the problem, but is too hard to fix. A ScrumBut retains the problem while modifying Scrum to make it invisible so that the dysfunction is no longer a thorn in the side of the team. A Better Path To the “Definition of Done” As more companies try to adopt ideas from Scrum, I notice that some have real trouble with the so-called “Definition of Done”.
This idea seems sensible: we define general criteria for what constitutes calling a story “done”. In part, we do this to avoid ongoing arguments; in part, we do this to give teams a goal to reach for; in part, we do this because the book tells us to do it. I’ve heard about and witnessed many well-meaning people adopt this idea, then create all manner of chaos for themselves. Personal Scrum. If you’ve been following my blog, you know that I have been using an adaptation of Scrum for a one-person team to manage my graduate project.
Understanding the Scrum Burndown Chart. Understanding the Scrum Burndown Chart Dusan Kocurek, ScrumDesk, www.scrumdesk.com Being a startup is a great period in the company’s lifetime.
Developing a product in which you believe with a small and highly motivated team is remarkable experience that you hope will stay forever. Successful products grow quickly in complexity terms that lead to more complex processes and metrics just to measure the progress ending up in non-usable results. The software industry is recognizable by high failures rate, late delivery, low quality, but still producing each day products used by millions of people. The Product Owner's Guide to Effective Sprint Goals. Working with a sprint goal is a powerful agile practice.
This post helps you understand what sprint goals are, why they matter, how to write and to track them. The Sprint Goal Explained A sprint goal summarises the desired outcome of an iteration. It provides a shared objective, and it states why it’s worthwhile undertaking the sprint. Sample sprint goals are “Learn about the right user interaction for the registration feature”, or “Provide the missing reporting functionality”. As a rule of thumb, every sprint should have one shared goal. Scrum (development) Scrum is an iterative and incremental agile software development framework for managing product development.
It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives.
An Introduction to Planning Poker. Planning Poker is an agile estimating technique which has become very popular in the last few years.
It is based on an estimation technique known as Wideband Delphi which was created by the RAND Corporation either in the 1940s or 1968 depending upon which sources you find credible. The technique was refined by James Grenning in 2002. It was made much more popular when it was included in Mike Cohn’s book “Agile Estimating and Planning.” Although the basics of the technique have been around for many years the refinements by Grenning made it usable by agile teams and they have taken full advantage.
RedistributableIntroToScrum. Writing use cases for agile (Scrum) projects. Today I started writing use cases for a software development project that are using Scrum.
I have written plenty use cases for projects earlier so I thought that this would be a nice task to do on a Friday. I grabbed a good cup of coffee, sat down, listened to Me first and the gimme gimmes on my headset and started writing. Suddenly I started thinking; this can not be in the spirit of agile development. Doing Agile Isnt The Same As Being Agile. Scrum Breakfast: Explaining Story Points to Management. During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?
" A good question, and in all honesty, developers can be an even more critical audience than managers. Traditional estimates attempt to answer the question, "how long will it take to develop X? " I could ask you a similar question, "How long does it take to get the nearest train station? The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically.
Scrumology - Agile coaching and training.
Scrum Master. Scrum bij grote projecten? Iedereen die eens gewerkt heeft voor een grote ICT-organisatie weet hoe moeizaam software-ontwikkeling kan verlopen.
Scrum is een softwareontwikkelings-methode die zo flexibel is dat tijdens het ontwikkelingsproces verandering mogelijk is. Dit in tegenstelling tot de traditionele ontwikkelmethodes waarbij aan het begin van het project het hele proces wordt uitgewerkt. Hierdoor kan het zijn dat een ontwerpfout pas vlak voor oplevering wordt ontdekt. En zo bestaat de kans dat het project uitloopt of zelfs faalt. Dit kan Scrum oplossen. Google, Bol.com en Knab doen het al. Combining Scrum, Kanban, and Scalable Agile Webinar [Video]
Combining Scrum, Kanban, and Scalable Agile Webinar [Video] Posted by adam feber on Thu, Mar 15, 2012 View and download the slides from the webinar here. Presentations - Scrumology. I’m asked every week about my best tools and resources to use for Scrum, building teams, technical practices and more, so I decided to put this list together. Did you know that there are over 6 different organizations offering agile certifications? A peek at Chapter 2, Agile Certifications. Do you know what those organisations are, or the pros and cons of the different certifications? And, what certification is right for you? Improving Agility: Agile Certifications is an overview of the major organizations offering agile certifications.
I believe certification is an individual choice with many factors to consider including education, career opportunity, personal growth, time and money.