Category Archives: DevOps

Four Point DevOps Story

Build team interest and passion in DevOps by promoting four DevOps themes:

  1. DevOps PaaS Delivers at the Speed of Business Demand
  2. DevOps Equals DevOps Principles Plus DevOps Practices
  3. The Agile DevOps PaaS Mindset
  4. ALM PaaS Bridges the Dev Gap

Every team member desires to fulfill their objective while delivering  at the Speed of Business DemandHigh performance IT teams move at the speed of business.

They rapidly deliver high quality software solutions that enable business penetration into new markets, create innovative products, and improve customer experience and retention. Unfortunately, most IT teams do not have an environment fostering the rapid iteration, streamlined workflow, and effective collaboration required to operate at the speed of now and capture business opportunity. Disconnected tooling, static environment deployment, and heavyweight governance across development and operations often impede rapid software cycles, minimize delivery visibility, and prohibit innovative experimentation.

A new, more responsive IT model is required!  

A more responsive IT model incorporates  DevOps Principles Plus DevOps Practices.

Every successful, long-lasting model has a clear manifesto outlining goals and principles. Many DevOps adopters may not be aware of the DevOps Manifesto (created by Jez Humble @jezhumble) nor how successful DevOps requires keeping a clear focus on principles, practices, and value (instead of infrastructure tooling.

When teams converge agile and DevOps practices with Platform-as-a-Service (PaaS) infrastructure, they adopt an agile DevOps PaaS mindset.  They create a collaborative environment that accelerates business enablement and increases customer engagement. Adopting agile devops requires a structural mind shift, and successful IT teams follow manifesto guidance to change delivery dynamics, take small steps to build one team, focus on real deliverables, accelerate reactive adaptation, and guide continuous loop activity.

Effective cross-functional teams drive every big success. Whether bridging dev with ops or biz with dev, encourage self-organizing teams and value small daily interactions.

ALM PaaS bridges the development gap between corporate IT and distributed outsourced development activities. The traditional gap impedes system integration, user acceptance testing, visibility into project progress, and corporate governance. Stephen Withers describes an often true, and ineffective current ALM state:

” the CIO does not have visibility of the overall project: this is a major problem.”

A top CIO desire is to obtain portfolio-wide visibility into development velocity, operational efficiency, and application usage.

What solution or best practices do you see solving balkanized, silo development tooling, fractured governance, disconnected workflow, and incomplete status reporting when working with distributed outsourced teams or across internal teams?

Recommended Reading

  1. DevOps PaaS Delivers at the Speed of Business Demand
  2. DevOps Equals DevOps Principles Plus DevOps Practices
  3. The Agile DevOps PaaS Mindset
  4. ALM PaaS Bridges the Dev Gap

 

pressreleasepoint.com.shadowIT

Embrace Shadow IT Clouds

Cloud is the new shadow IT for enterprises. While stable, well-known SaaS offerings such as Salesforce or Netsuite are excellent paths forward,  unregulated, shadow IT cloud deployments often expand  business risk and magnify IT inefficiencies.   According to a recent TechRepublic report, shadow IT departments can create major fiscal problems for businesses using the cloud.  A PressReleasepoint.com release points to the source of increasing shadow IT cloud deployments:

Leasing cloud servers and subscribing to applications is incredibly easy. There is no reason why a business manager, customer service representative or other non-technical employee cannot quickly establish a cloud deal and start using an application because he or she thinks it will get the job done effectively. This is precisely why IT oversight is necessary.

Shadow IT teams gain faster time to market and decrease delivery hurdles by running home-brewed business critical systems on AWS, Heroku, Cloudbees, Azure and other cloud platforms. Often enterprise IT only discovers Cloud systems existence when the Shadow IT project requires access to  enterprise system data or services.

To co-exist with Shadow IT and maximize Cloud efficiency and productivity,  align corporate IT policy, architecture, operations, and support with innovative, shadow IT projects . Are you an expert at working with Shadow IT?

Continue reading

WSO2 App Factory

The Agile DevOps PaaS mindset

When teams converge agile and devops practices with Platform-as-a-Service (PaaS) infrastructure, they create a collaborative environment that accelerates business enablement and increases customer engagement. Adopting agile devops requires a structural mind shift, and successful IT teams follow manifesto guidance to change delivery dynamics, take small steps to build one team, focus on real deliverables, accelerate reactive adaptation, and guide continuous loop activity.

Continue reading

DevOps Days

DevOps Equals DevOps Principles Plus DevOps Practices

Successful, long-lasting movement have a clear manifesto outlining goals and principles.   Many DevOps adopters may not be aware of the DevOps Manifesto (created by Jez Humble @jezhumble)  nor how successful DevOps requires keeping a clear focus on principles, practices, and value (instead of infrastructure tooling.

DevOps Principles

DevOps value is derived in the core principles that started the movement:

  • Iterative
  • Incremental
  • Continuous
  • Automated
  • Self-service
  • Collaborative
  • Holistic

Teams should analyze existing processes against the principles, and see where DevOps practices can add value.

 

DevOps Practices

A few identified DevOps practices include:

  • Self-service configuration
  • Automated provisioning
  • Continuous build
  • Continuous integration
  • Continuous delivery
  • Automated release management
  • Incremental testing

DevOps Tool Capabilities

As Mike (@madgreek65) and Abel (G+AbelAvram) mention, teams commonly focus on tools instead of value. DevOps friendly tooling delivers:

  • Self service project via project configuration portals
  • Policy configuration for Security, service levels, frameworks, usage, topology concerns
  • Automated platform provisioning via service tier templates, frameworks, and policy enforcement points (PEP)
  • Process automation with Continuous build, test, and deployment. Code promotion and synchronization across environments and servers
  • Dependency analysis and impact analysis

DevOps Value

For value metrics, break up DevOps goals into foundational, optimal, and transformational categories. For example,

Foundation

  • Time and effort to create new application environment
  • Time to redeploy application
  • Time to promote application into a new lifecycle phase

Optimize

  • Dynamically right-size infrastructure scale
  • Re-use existing platform services and business services from resource pool instead of re-building solution stack

Transformation

  • Time and effort required integrating business process, event processor – creating a complex app.
  • Time and effort required to apply policy across tenant(s)
  • Cost to operate application per user or transaction

 

Keep a DevOps Focus

So look beyond adding the cool ‘DevOps Engineer’ title and tool names (i.e. Puppet, Chef, Ansible, and Salt) onto your resume.   DevOps is about principles, practices, and creating a collaborative environment that improves software delivery and increases business value.   With good information readily available on the Web, and conference series (for example, DevOpDays ) focused on core DevOps principles and practices, you can stay tuned into the DevOps way of thinking!

DevOps Days

Feature Image Courtesy of DevOpsDays.org

Cloud DevOps and The Path Towards Governance

Cloud DevOps and PaaS are paving a path towards teams adopting governance best practices.  Teams often follow human nature and take the path of least resistance.  DevOps automates activities, and with adequate up-front planning, DevOps can make ‘the right thing to do the easy thing to do’.

Governance is the precepts, policies, processes, and tooling used to conform activities, minimize risk, and maximize effectiveness.   As Mike Kavis states in a recent blog post,

  Many IT and DevOps shops always look at governance as a dirty word because it sounds too much like government, which sounds too much like bureaucracy and waste. The problem with governance is not with governance itself, but with how organizations have tried to implement (or not implement) it.

 

DevOps principles and practices combined with PaaS characteristics will quicken IT solution development and delivery.   A DevOps focus on continuous activity execution (e.g. continuous build, continuous integration, continuous test, continuous delivery) creates a ‘no wait’ environment.   Teams do not have to wait for the next script to run or for the next activity to commence.  By incorporating automation into developer and operations processes, teams bypass time consuming manual tasks and gain faster phase execution.  Both DevOps and PaaS promote simple, on-demand self-service environments that shield team members from complexity and reduce skill hurdles.  By offering on-demand self-service access, rapid business innovation and experimentation is possible. By reducing complexity, team members are not required to obtain special training and skills before consuming IT services and infrastructure.

A configurable DevOps PaaS can implement governance best practices and be readily adopted by teams without extensive implementation effort.  Effective application delivery governance presents a simplified and unified user experience to complex development tools, processes, and team hand-offs.  By integrating software promotion best practices, test automation, continuous integration, and issue tracking, application delivery governance raises software quality while reducing delivery timeframes.  For more information, read about how to accelerate agility and maintain governance with DevOps PaaS

Recommended Reading

 

Adopting DevOps and Governance Webinar

Application Services Governance requires more than a SOA Registry

Application Services Governance

 

Change your IT Value Proposition: Build the Plan, Work the Plan

Looking to reshape your IT value proposition, and feel legacy application platform, service infrastructure, or integration infrastructure is holding you back? Let’s talk about how the WSO2 advantage can transform your projects’ experience.    What our your goals, challenges, and constraints?

When building a plan for 2014, consider:

  • Re-shape Enterprise Architecture
  • Re-invent the Integration Platform

 

Continue reading

How can Everytown IT adopt DevOps and achieve business benefit?

Donnie Berkholz has an excellent blog post describing why EveryTown IT hesitates to adopt DevOps and Cloud, even though they realize significant business benefit may be achieved.   Donnie describes how EveryTown IT lives in:

a world where inertia rules the day, where business is king and sysadmins have little to no say in major changes. And it’s a world where even experimentation is difficult and must be done on the smallest of scales.

Sound familiar?

Continue reading

New IT model

A New IT model is required to reduce delivery time and accelerate business agility. The New IT Delivery model strives to achieve open collaboration, micro-iterations, no wait states, and streamlined processes.

 

How are you building a pragmatic, open source driven game plan that incorporates New IT approach vectors?

 

The path to New IT requires incrementally moving away from traditional application platforms, traditional team structure, and traditional information flows.  The New IT architecture underlying Responsive IT intelligently incorporates Cloud Platforms, BigData Analytics, Enterprise DevOps, and API first development.

Continue reading