Archive

Posts Tagged ‘burndown chart’

Agile Scrum Project Status Reporting

April 28th, 2009

sharewritten by gunther gerlach-2009

Obviously the daily stand-up (or daily ) is a good form of . It’s great for people with a close interest in the project who can spare the time to get to the . But it’s really no good for other that can’t get to the each day, either because they are interested in less detail, or because they have an interest in many projects and can’t be at all the scrums.

Gunther Gerlach

Implementing Scrum

April 28th, 2009

sprintwritten by gunther gerlach-2009

Define your : A Sprint is a key when agile process is implemented in SDLC. The Sprint defines the amount of time where a team will release a feature or list of features from a giving sprint backlog. This is an important decision. suggests 30 days, but they could a week if you estimate that will improve your team efficiency. The optimum depends on many factors. I suggest going back to your team and analyzing the perfect duration to be able of releasing a piece of software. I suggest 14 days, plus a planning day for your team and Stake Holders to create the prioritize requirements form different teams and, analyze the product burn chart. This will leave 2 weeks of intensive work and also, two Sprints a month.

Gunther Gerlach