Skip navigation

Category Archives: XP

Standards for Scrum:
• A Scrum team must have a Product Owner and know who that person is.
• The Product Owner must have a Product Backlog with estimates created by the team.
• The team must have a Burndown Chart and know their velocity.
• There must be no one outside a team interfering with the team
during a Sprint.

Scrum and XP teams don’t pursue drawing the perfect UML model in a case tool, writing the perfect requirements document, or writing code that will be able to accommodate all imaginable future changes. Instead, Scrum and XP teams focus on getting things done. These teams accept that they may mistakes along the way, but they also realize that the best way to find those mistakes is to stop thinking about the software at the theoretical level of analysis and design and to dive in, get their hands dirty, and start building the product.

Scrum is not a methodology, it is a framework. What that means is that Scrum is not really going to tell you exactly what to do. Darn.

How we do product backlogs
The product backlog is the heart of Scrum. This is where it all starts. The
product backlog is basically a prioritized list of requirements, or stories, or features, or whatevers. Things that the customer wants, described using the customer’s terminology. Important that’s in shape when the team sees it

Our stories include the following fields:
ID – a unique identification, just an auto-incremented number.
This is to avoid losing track of stories when we rename them.

1) Where to start (at the begining there was nothing!):

The starting point: ^^

 2) Learn the agile methodologies principles

Search, learn and study for a little while (so the agile terms light a bulb in your head)

 3) See it on the real world -> (From theory to the real world)

A very useful online_free book about Scrum & Extreme Programming:  Scrum XP from the trenches available at: by Henrik Kniberg

Another useful book by the same author:

Kanban+Scrum = ScrumBan at

 Some comunities:

Some Quotes:

“There is surely nothing quite so useless as doing with great efficiency that which should not be done at all” -Peter Drucker