SCRUM - Morten Nielsen

Morten Nielsen

Sign in Subscribe

SCRUM

A collection of 10 posts

A pull process

While reading The Power Of Pull, [http://www.amazon.com/Power-Pull-Smartly-Things-Motion/dp/0465019358] I came to think about push and pull processes. Now the definition of these is not the same as a push or pull process as used in that of lean processes, instead here a pull process regards

Inventory in software

I’ve been thinking a bit about all these factory references that occur when discussing software development. So here is an inventory management view, I guess. Inventory, viewed from a lean perspective is waste. If you can keep your process running with minimal inventory, then you can decrease costs for

Sprint startup

A while back we started with one-week sprints. For several reasons. We had four-week sprints earlier, but sometimes it was unclear what we were supposed to deliver and what we delivered. Today we started our third one-week sprint. The start-up meeting took 20 minutes, and was a stand up meeting.

New sprint

We started a new sprint today. This sprint were doing some finishing touches to the hierarchies I posted about earlier, and were touching up on filters. Were introducing logs on some domain entities, allowing users to track changes to the entity and actions related to it. Hopefully its all wrapped

Knowing the problem domain of a project

When working with long running software projects. The initial stakeholders and developers often leaves before the project is complete, if it ever becomes completed. As a result, the inital decisions made when starting the project can be forgotten. The experiences that lead to the project being initiated in the first

A positive aspekt of RUP

Ive been working on a business plan for a business plan contest recently. It’s the first time that I write a business plan and to be honest, its opened my eyes on many different levels. Here is a conclusion I came to after mentally going over the RUP project

Technical team-building

I firmly believe that; if a team has a common view of how software is to be developed. The team can produce software a lot faster. If not only for the fact that if the team shares a common view of how code is structured, in an object-oriented sense, then

How to communicate Hot-fix cost

Ever had problems with the communication between the customer and the development team, due to hot-fixes? Hot-fixes, deliveries that are not part of the planned release cycles are a burden to the entire release process. I personally believe that the cost of the hot-fix isn’t worth it, instead focusing

The process evolves from below, not above

Remember, it is the people that are working with a process that evolves it. Changes to a process should come from a need by those whom work within it. I firmly believe that this is the only way a process can continue to evolve without breaking. This also means that

Scrum and the value of money

I had this discussion at work the other day, about teaching your kid the value of money. Well I have a kid at home, I cant say in the age where I have to worry about it. But what I also have athome is a SCRUM task board. Me and