background preloader

SAVE

Facebook Twitter

Bigdata. INVEST in Good Stories, and SMART Tasks. (French) In XP, we think of requirements of coming in the form of user stories.

INVEST in Good Stories, and SMART Tasks

It would be easy to mistake the story card for the "whole story," but Ron Jeffries points out that stories in XP have three components: Cards (their physical medium), Conversation (the discussion surrounding them), and Confirmation (tests that verify them). A pidgin language is a simplified language, usually used for trade, that allows people who can't communicate in their native language to nonetheless work together. User stories act like this. Scrum Reference Card. Print version A Management Framework Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams of about seven people each.

Scrum Reference Card

It provides a structure of roles, meetings, rules, and artifacts. Teams are responsible for creating and adapting their processes within this framework. Scrum uses fixed-length iterations, called Sprints, which are typically 1-2 weeks long (never more than 30 days). Scrum Training Series: Free Scrum Master Training. What powerful questions does Scrum help you answer? The video on powerful questions made me think about the deeper purpose of the various Scrum activities.

What powerful questions does Scrum help you answer?

Can I formulate Scrum as a series of Powerful Questions to be general enough, that they might be useful outside of software development? Here is the image I came up with and below are the questions I think each of the Scrum Activities and artefacts strives to help you answer. Sprint. Technos / Skills trends. Getting Value out of Agile Retrospectives. Hi guys, I want to use this post to introduce a topic I will discuss during next few weeks.

Getting Value out of Agile Retrospectives

Me and my colleague Ben Linders we are writing a pocket book about agile retrospectives. The title of this book is: “Getting Value out of Agile Retrospectives“. The main target are: Agile coaches, scrum masters, project or product managers or facilitators who have at least some experience with doing agile retrospectives. They know the purpose of them, how they fit into agile / scrum, and how to arrange and perform them. This book will deliver practical description of agile retrospectives and how to do them, as well as an inspiration to different agile retrospective techniques and good practices in doing them.

Retrospective fatigue? How to increase follow-through on action items. The retrospective is my personal favorite among the Scrum meetings.

Retrospective fatigue? How to increase follow-through on action items

Why? Even if there were no other meeting, role, or artefact, retrospectives enable you to invent everything else you need to improve. In theory at least. When I was just learning how to facilitate retrospectives, I was mainly concerned about the flow of the actual meetings. Fun Retrospectives. Suggested Topics for Definition of Done Discussion.

Ken Schwaber and the rest of us advocate paying attention to what “done” means for a Product Backlog Item (PBIs, or “stories”).

Suggested Topics for Definition of Done Discussion

For a lot of programmers (like me), “done” often means “It works on my workstation!” The Scrum Master is charged with advocating a “done” that includes everything else needed to build a potentially-shippable product increment. Scrum 3.0 and Organization 4.0 - impressions from a great evening with Boris Gloger at ImmobilienScout24. Today I had the opportunity to join a great and inspiring presentation by Boris Gloger talking about Scrum 3.0 and organization 4.0 (thanks to Immobilienscout24 for hosting a great event).

Scrum 3.0 and Organization 4.0 - impressions from a great evening with Boris Gloger at ImmobilienScout24

With this post I provide a short summary of my notes and insights and links to further posts I already wrote about some topics presented today. Based on an initial blog post by Boris (DE) - we started today with a recap of the Scrum journey from Scrum 1.0, Scrum 2.0 and developed to today's Scrum status. Scrum 1.0 foundation by e.g. Agile Software Development with Scrum (Ken Schwaber)basic meeting artifacts, 3 roles (ScrumMaster as management role, Product Owner and team)retrospective was not yet part of itBacklog idea, but not yet that establishedfocus on deliverysprint idea - a common way to think about what we would like to deliver together, but breaks in between sprintslong Excel-lists with tasks and detailed task estimations.

Gamestorming – A toolkit for innovators, rule-breakers and changemakers. Scrum Methodology & Agile Scrum Methodologies. Gamestorming – A toolkit for innovators, rule-breakers and changemakers.