Translating Product Backlog into Sprint Backlog
Every 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 Product Backlog is then allowed to grow and change as more is learned about the product and its customers.
How Cloud Computing change your Software Architecture?
Basically, moving to the cloud it shouldn’t impact your architecture with many changes as we believe. If your platform has a well design architecture based on independent layers (UI, Logic, Data, etc), adapting to work in a Cloud environment only mean to add a new layer of virtual environments to your n-tiers environment. Moving to the Cloud only become a problem when solutions don’t have a solid and well designed architecture and basically they are pushed back at the moment to adapt to this new age of technology.
Options for your Virtual Infrastructure
written by gunther gerlach-2009
I have talked about virtualization and also about Cloud Computing but, what options are available to implement cloud computing Infrastructure implementations? Well, that is simple!
Hardware technologies for virtualization (hypervisor)
Hypervisor Virtualization has a layer (usually a thin Linux kernel shown here as a hypervisor or standard OS) that is loaded directly on the bare server. To allocate hardware and resources to the virtual machines (VMs), all hardware on the server must be virtualized. The next layer up shows each chip, board, etc. that must be virtualized so that it can be assigned to the VMs. Once in the VM itself, there is a complete copy of an operating system and finally the application or workload.
Click here for more details!
Günther Gerlach
EXECUTIVE LEADERSHIP: World-Class Development Organizations, Web-Services, E-Commerce, IT Operations, Scalable Cloud Computing, Tier-1 Systems.
Highly accomplished executive with 10+ years of experience directing high performance enterprise web-based solutions. Proven executive leader cultivating relationships at the SVP and C-level plus with the ability to train and lead cross-functional onsite and international teams leading initiatives being developed by up to 230 engineers driving the design and execution of critical components for Amazon global systems architecture and its Enterprise Elastic Computer Cloud (EC2) plus inter-dependent SAP integration solutions for DHL Express. Combines technical skills including proficiency in 12 programming languages with visionary business acumen to create strategic enterprise-wide alignment. Managed Budgets up to $22 MM. Entrepreneur successfully opened and directed a technology retail company. Trilingual: English, Spanish, Italian.
Architectural Tips for Infrastructure as a Service (IaaS)
written by gunther gerlach-2009
Evolving application architectures just as P have shown that cloud computing is a natural extension of current trends and best practices, the same is true when viewing cloud computing from an architectural perspective. Again, cloud computing is nothing new, yet in its implementation, it changes everything that we do.
Changing application designs In the past, applications were built to handle larger workloads through vertical scaling. Put more processors and memory on a mail server to handle a larger volume of traffic. Scale up a database server to increase throughput. Run high-performance computing jobs on a supercomputer.
Key Features for User Story Implementation
written 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 INVEST model 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.



