The Scrum Primer

Living these holidays a good way: reading books!

Going again the Scrum road, because of this book The Scrum Primer (available here)
New to Scrum? short eperienced?
this book helps you understand better what Scrum is for, also strenghtness and weakness compared to your context.
It helped me clearing couple of foggy areas I always wanted to know more about,
in example: do PO is a lone person? or is it better if shared among some people? … being a PO is a job that comes with great honor but greater responsibility, “life” of product backlog, when&where priorities can changes, dev team duties, sprint’s length, sprint review (it is not just a demo), definition of done (remember potentially shippable product) … and much much much more I don’t want to reveal

There are also some areas I’d read more details about: sprint review, sprint retrospective, daily duties of scrum master, cooperation among the whole scrum team …

More than just the usual blog post, article, etc … this short ebook worth a couple reads

thanks to Fabio Armani for sharing this ebook

source: The Scrum Primer (by InfoQ)
source: Scrum Primer (via linkedin)

Technorati tags: Agile, Scrum

Microsoft TFS 2010-2012 and templates (Scrum, MSF Agile) … useful TFS 2010-2012 links

If you are looking for TFS templates, MSF Agile and Scrum, you’ll find lot of info of course.
Furthermore, recently TFS Service has been release, with its Scrum 2.1 and MSF Agile 6.1 templates.

Here is my short bookmarks list, hoping it saves your time:

• Team Foundation Server Service
• TFS 2012 certifications
• What’s new in the Visual Studio Scrum 2.1 Process Template?
• Implementing Scrum Using Visual Studio 2012 lok to bottom links (Visual Studio Scrum 2.0 process template (RTM) | ScrumRobot (for TFS2012 RC))
• Useful TFS Links
• How are tests handled by Scrum using TFS 2012?
• TFS 2012 Scrum 2 – Best configuration for Areas, Iterations, backlog iteration, sprint iteration
• Migrating Scrum for Team System 3.x to MS Scrum 2.0
• TFS 2010: MSF Agile vs. Visual Studio SCRUM 1.0 Smackdown
• TFS 2010: MSF Agile vs. Visual Studio SCRUM 1.0 Smackdown– Planning w/ Agile (Part II)
• TFS 2010: MSF Agile vs. Visual Studio SCRUM 1.0 Smackdown — Planning w/ Agile (Part III)
• A Scrum comparison of the MSF/Agile and Visual Studio Scrum templates (MSF/Agile 5.0 VS Scrum 1.0)

Technorati tags: Agile, Scrum, TFS

Kanban: Successful Evolutionary Change for Your Technology Business

Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson .

Amazon.com:

Kanban is becoming a popular way to visualize and limit work-in-progress in software development and information technology work. Teams around the world are adding kanban around their existing processes to catalyze cultural change and deliver better business agility. This book answers the questions: What is Kanban? Why would I want to use Kanban? How do I go about implementing Kanban? How do I recognize improvement opportunities and what should I do about them

What do I say?
Practical guide to Kanban, with good examples, pinches of Scrum in some parts.
Read it more than once

Technorati tags: Agile,Kanban

Kanban: Successful Evolutionary Change … highlights #7

From KANBAN: Successful Evolutionary Change for Your Technology Business
Triage

[...] Triage is a term borrowed from the medical profession; it refers to the practise of assessing and classifyng emergency patients into categories for priority of attention. [...] Triage was adopted into software development for classifying defects (bugs) [...]

This book tells about Kanban (capital K), also about Team Foundation Server … the steps before TFS

source: KANBAN: Successful Evolutionary Change for Your Technology Business

Technorati tags: Agile, Kanban, TFS

Kanban: Successful Evolutionary Change … highlights #6

From KANBAN: Successful Evolutionary Change for Your Technology Business

The “After Meeting”

[...] There is an interesting difference between this emergent Kanban (*) process behavior and Scrum. With Scrum, the team meet first and then send a delegate to a Scrum-of-Scrum to coordinate a program or large project. In Kanban the behavior is reversed-the program-level meeting happens first. [...]

(*): please note capital K: Kanban is not kanban

source: KANBAN: Successful Evolutionary Change for Your Technology Business

Technorati tags: Agile, Kanban