Archive

Archive for the ‘Project Management’ Category

Lean applied to Software Development – Stop Wastes and Defects

December 6th, 2009

rightWhen one looks at all the , defects has to be the most obvious one. The cost and repercussions of finding defects varies depending on where in the cycle they’re found. Defects found early on in the life-cycle are way less costly to resolve than defects found later on in the cycle; the most expensive being when applications are already in-production.

Additionally, depending on when the defects are found, defects can and do trigger other like task switching, relearning etc.

Gunther Gerlach

Translating Product Backlog into Sprint Backlog

December 6th, 2009

z-cubes1Every time a project is initiated there is no understanding, time-consuming effort to write down all foreseeable tasks or requirements. Usually, a project writes down what is obvious, which is almost always more than enough for a first sprint. The is then allowed to grow and change as more is learned about the product and its customers.

Gunther Gerlach

Key Features for User Story Implementation

July 8th, 2009

z-stepswritten by gunther gerlach-2009

A user story describes desired functionality from the customer (user) perspective. A good user story describes the desired functionality, who wants it, and how and why the functionality will be used.

The define a User Story as Independent, Negotiable, Valuable, Estimable, Small, Testable. Let’s see what each one means:

Independent - One user story should be independent of another (as much as possible). Dependencies between stories make planning, prioritization, and estimation much more difficult. Often enough, dependencies can be reduced by either combining stories into one or by splitting the stories differently.

Gunther Gerlach

How does a Project Manager add value to an Agile Scrum team?

July 7th, 2009

z-share written by gunther gerlach-2009

Definition: Agile project management is as radically different from traditional project management as are different from traditional methodologies. Rather than plan, instruct and direct, the agile project manager facilitates, coaches and leads.

 

Recently I came across of someone posting about the value of a PM in an environment. It’s been a long time from most of the companies realized the important role of PMs But it looks like some Scrum process consultants, after run out of ideas to justify the PM’s role, they just wants to get rid off them… big mistake

Gunther Gerlach

Service Quality Management

June 22nd, 2009

z-cubeswritten by gunther gerlach-2009

In wider spanning , several service providers may offer functionally replaceable services that differ in their extra-functional characteristics, such as usage terms and quality of service delivery. Service providers need to be responsive – potentially in real-time – to negotiate variations of service delivery requirements (e.g., price, deliverable timetable). should therefore explicitly support the negotiation process, reducing non-critical human involvement and providing decision-makers with the information they require to formulate and assess service offers.

Gunther Gerlach

How to measure your team and project velocity?

May 16th, 2009

z-velocitywritten by gunther gerlach-2009

Velocity is a measurement of how much the team gets done in an iteration (called as Sprint in ). Velocity is what actually got done in the last iteration not what is planned and is calculated by the number of done in a certain sprint.

In Scrum it is measure in . Each feature in scrum is a story. A story has points. Points can be anything you come up with.

Examples are 1, 2, 4, 8 , 16

aa

Gunther Gerlach