Cloud Computing Architecture
written by gunther gerlach-2009
Quick definition: Cloud Computing 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 software as a service (SaaS), and other well-known technology trends.
Cloud computing 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 cloud computing.
Understanding Your Project Velocity
written by gunther gerlach-2009
Project Velocity is terminology from the Agile Scrum methodology and is basically the same concept as Earned Value in more traditional project management methods.
How it works: Select a regular time period over which to measure project velocity. If you’re using fixed Sprints 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 story points. 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.
Agile Scrum Project Status Reporting
written by gunther gerlach-2009
Obviously the daily stand-up (or daily scrum) is a good form of status reporting. 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 stakeholders 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.
Create the Product Backlog
written by gunther gerlach-2009
The Product Backlog, 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 Product Backlog. Anyone. The agile Scrum process, and agile development principles generally, are collaborative and inclusive. There is no longer any need to say no.
Only the Product Owner can prioritize the Product Backlog.
The Product Backlog can contain anything. Anything relating to the product that is. Bugs. Enhancements. Whole projects. Issues. Risks. Anything. Having said that, items on the Product Backlog should ideally be expressed in business terms that are of some value to the user (or customer, or business). Not as technical tasks.
Estimating in Agile Scrum Software Development
written 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 story points from Fibonacci numbering system, however this approach only work when features are similar enough to keep a project velocity chart (average project velocity 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 project velocity 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.


