Chose categories and files from the sidebar!

Cloud Computing Architecture

May 1st, 2009

cloudinfraswritten by gunther gerlach-2009

 

Quick definition: is an Internet based platform geographically distributed and developed to provide real-time scalable resources and provided “as a service” over the Internet to users who don’t need to have deep knowledge or expertise on technology infrastructure. The concept incorporates (SaaS), and other well-known technology trends.

 

services span a wide scope, from virtualized low-level computing and storage to full business services. Understanding the spectrum of cloud services and the characteristics of each service category is essential in determining when, where, how and why to apply .

Gunther Gerlach

Understanding Your Project Velocity

April 28th, 2009

velocitywritten by gunther gerlach-2009

is terminology from the  methodology and is basically the same concept as in more traditional methods.

 

How it works: Select a regular time period over which to measure . If you’re using fixed or iterations, use that time period. Otherwise you can use weeks, fortnights or months. It doesn’t really matter which as long as you’re consistent. Add up the estimates for all the tasks/deliverables/features in your chosen time period. It doesn’t matter whether the estimates are in days, hours or even in relative . Only include the estimates for any items that are 100% complete and signed off within the time period. Anything still in progress counts as zero, as there is no value in incomplete work.

Gunther Gerlach

Agile Scrum Project Status Reporting

April 28th, 2009

sharewritten by gunther gerlach-2009

Obviously the daily stand-up (or daily scrum) 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 scrum. But it’s really no good for other that can’t get to the scrum 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

Create the Product Backlog

April 28th, 2009

createwritten by gunther gerlach-2009

 

The , in its simplest form, is a list of things that people want to be done to the product, in priority order. Anyone can add anything to the . Anyone. The process, and agile development principles generally, are collaborative and inclusive. There is no longer any need to say no.

Only the can prioritize the .

 

The can contain anything. Anything relating to the product that is. Bugs. Enhancements. Whole projects. Issues. Risks. Anything. Having said that, items on the should ideally be expressed in business terms that are of some value to the user (or customer, or business). Not as technical tasks.

Gunther Gerlach

Estimating in Agile Scrum Software Development

April 28th, 2009

z-estiwritten by gunther gerlach-2009

 

There are many approaches for the estimation of a project. Some people will tell you to use the estimation based on from , however this approach only work when features are similar enough to keep a chart (average per sprint) in your project but, we all know that this is impossible, some features will need less than a hour of development and other sometimes two days. I am not saying that this methodology is not good, I am just saying that is perfect to get your chart from the project but if you really want an estimate to get the cost and scope from your project you need the estimate in a period of time, usually days of work.

Gunther Gerlach