we produce both: code and knowledge

Being a product owner recently I had a discussion with one of the key developers in my team: I reported back an issue (as a user story) and he claims that previously we had agreed on a different solution and now I am changing my mind, and these changes will take quite a big effort.

I understand his concerns, developers don't like to re-work. Who likes?
But my reply is that the time spent on this curve is not wasted, rather it is spent on producing the knowledge.

We produce both: code and knowledge, and this is what software is.

The waste is when no knowledge, no code or no other useful artifacts are produced, otherwise it is investment.

Catalog of Scrum smells

User Stories for scrumsmells.com project

Users

• SP - Scrum practitioner
• Admin - Site administrator
  

Backlog

MUST

• As an SP, I can see an intro to understand why this site is useful
  
• As an SP, I can view the list of smells
• As an SP, I can select a particular smell and see its details
• As an SP, I can add a new smell
• As an SP, I can get a permanent link to a particular smell to share it with other people

SHOULD

• As an SP, I can see the area(s) that the smell related, e.g. "Meetings", "Spring Planning", etc
• As an SP, I can see smells grouped by areas
  
• As an SP, I can see links related to a smell that I am watching

COULD

• As an Admin, I get notified when a user posts a new smell
• As an SP, I can provide more links to an existing smell
• As an Admin, I get notified when a user adds new a link to a smell
  

Links

Published scrum smells on the web:

• a page of Scrum alliance on smells
  
• toward a catalog of Scrum smells, Mike Cohn

Scrum gathering in Kiev 2007.

The 1st Scrum gathering in Kiev is to be held at the office of Ciklum in January-March
(the exact date is to be defined)

The agenda should be defined as we get results from the survey of the attendees.
The preliminary agenda is

Scrum start-up

1. why Scrum ? introduce Scrum for people who are new to it, define benefits why for team, why for customers
   
2. how to start Scrum? provide patterns of starting the 1st sprint
3. why Scrum is difficult? provide a set of examples to let better understand why it is not that easy to do Scrum
   
4. Scrum and requirements management provide different patterns including the approach with user-stories
5. case study: play a Scrum project
   
6. ... to be extended

Scrum complex topics:

1. effective planning meetings
2. effective Scrum retrospectives
3. ...to be extended