Enterprise Cloud Development (ECD) is being introduced as a new category or social construct within the software development industry. ECD is comprised of a five step pathway. The pathway is not so much a market maturity model as it is a business line capability model. The five steps are defined as:
Step 1 – Embrace the Cloud. This step is about organizing your data and aggregating the data sets so that they can easily be traced or reported upon. Whether you are a new team member on a team or an attorney looking for a code that has been listed in a lawsuit knowing where to find your data is the first step in being able to do something with that data.
Step 2 – Implement Community Architecture. As Brian Behlendorf (Founder of the Subversion and Apache open source projects) and Tim O'Reilly (founder of O'Reilly Media) explored in late 1990s there is a unique magic found in creating open source communities behind the corporate firewall. Through associations of data you can begin building conversations and architecting communities and threading stories around code, conversations or documents that relate to the software development lifecycle (SDLC). Since the late 1990s terms like Innsourcing larger than companies like Phillips (now NXP), Sun Microsystems or Motorola who implemented community architectures. In the late 2000s organizations like Red Hat, Inc. or the consultants at Olliance Group began adopting the term innersource and further validated Behlendorf and O'Reilly pioneering thinking leadership. This work has been furthered by folks like Dan Pink who analyzed the open source industry to unforgettable the mysteries of what motivates and drives us to excel and innovate at work.
Step 3 – Codify Development Processes. Once your data has been aggregated and your innersourced community has beenarchitected you can begin to realize how you do your work – this contemplation is often called process. Today Scrum, eXtreme Programming and Kanban are among some of the most popular processes to choose from for software development teams. What's more business lines or organizational transformations can be through step Step 3. Process change agents believe that reflecting organizational change can begin with process because of the link between process and culture.
Step 4 – Orchestrate DevOps. The idea is simply that development teams and traditional IT Operations groups are joining forces and will soon coexist on one team. One acid test of software development teams maturity is to see how close your development and IT Operations teams are. Here's a hint: the closer, the better.
Step 5 – Leverage Hybrid Cloud. Hybrid cloud infrastructures are infrastructure's that utilize both private (behind the firewall) and public (beyond the firewall) clouds to do different types of software development. For example developers on a team may utilize and internal tooling infrastructure to trace community based conversations but also utilize the Amazon.com EC2 public cloud for elastic on demand testing from seven global locations. Teams utilizing a hybrid strategy are seen as advanced.
Software development organizations can utilize this social construct or blueprint as a means of gaining capabilities and moving from one step to the next or in the hopes of making technology or process improvements. Enterprise Cloud Development assessments are now becoming readily available.
Source by Laszlo Szalvay