Skip to main content

AgileSoftwareDevelopment.com

When I started blogging, my (personal) objective was to make it easy for people who might be interested in my services to find me -- I figured they can find me easier than I can find them.

As the Scrum Breakfast blog has developed, it has taken on a life of its own, leading to invitations to do interesting things with interesting people. One such invitation came from Artem Marchenko, publisher of AgileSoftwareDevelopment.com, the online journal of Scrum and XP software development.

Today I start as a regular contributor to ASD, focused on Scrum and Scrum coaching. My first article, Start with Trust, Start with a Retrospective is now online for your reading pleasure.

Thank you Artem for this opportunity, I'm really looking forward to interesting articles and interesting discussions! To your readers, I look forward to their comments and their suggestions for topics!

P.S. You can view my ASD blog online or subscribe to it.

Update

Archem informs me that there is a DZone widget on all the ASD articles including including mine — just on the web site, not on the feeds. Obviously you are free to vote or not, but I wanted you to be aware that just 5-7 votes are typically needed for the promotion to the DZone front page. Such a promotion typically means 100-500 extra readers. And with such a small number of votes needed, every vote counts. So please vote if you like the article! Thanks!

Comments

Artem Marchenko said…
Welcome, Peter!

I am sure, everybody wins if more people will be able to find well prepared knowledge packs (articles) easier :)

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …