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

Anonymous 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

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…