Tag 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

 

WSO2 App Factory

DevOps PaaS delivers at the speed of business demand

High 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.

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

Application Services Governance best practices accelerate safe delivery

Application Services Governance is a mechanism to achieve business agility, build a responsive IT organization, and optimize IT effectiveness. Effective governance automates IT best practices, improves service levels, and facilitates safe, rapid iterations. Governance facilitates safe and rapid change by mitigating risks and reducing uncertainty when teams evolve IT systems. When enhancing governance effectiveness, successful teams smartly remixes IT skills, tooling, and processes; development and operation teams adopt agile processes, introduce automation tooling, and streamline collaboration.

Application Services Governance spans services, APIs, and applications. Don’t fall into governance gaps! Effective governance initiatives unify SOA governance, API governance, application governance, security governance, development governance, and infrastructure governance into a comprehensive and interconnected DevOps perspective.

To learn application service governance strategy and tactics, read the guidance at

 Application Services Governance Automates Best Practices

SOA Governance Requires More than A Registry

 

 

 

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

DevOps Ticket Reduction

A reduction in DevOps tickets not only drives IT efficiency, but also creates a cultural shift where teams look forward to rapidly achieving accomplishments.  Business stakeholders operate in an agile environment where no change request is too small, and rapidly testing business ideas is the new normal.

As a techie, I like to focus on the technology and IT process side of DevOps; bouncing around terms like ‘infrastructure as code’, ‘automated provisioning’, ‘continuous deployment’, and ‘continuous integration’.   The value-prop is self-evident to me and many of my peers. Yet, for us to change corporate culture and rally around a New IT Plan, the main message focus must not be  ‘DevOps for DevOps Itself’, but to create a Responsive IT team that changes business-IT dynamics and accelerates business agility.

 

Continue reading

Accelerating Business Agility with App Factory DevOps PaaS

Queuing, waiting, and the status quo doesn’t fit well with today’s now generation. Business stakeholders, who drive revenue growth and customer retention, desire to rapidly seize opportunity and market share.  They often view IT timeframes and capabilities as a poor match for today’s fast business-pace.  A New IT model is required to reduce delivery time and accelerate business agility.  DevOps PaaS brings no waits, faster phase execution, widespread accessibility, rapid grassroots innovation, and increased resource availability to IT projects.

Continue reading

DevOps meets ALM in the Cloud – Cloud DevOps Factory

Since teams started creating applications and services, significant challenges have continually hindered effective delivery and diminished development team’s reputations. Common challenges include:
  • Long IT solution lead times leading towards an inability to capitalize on business opportunities
  • Complex and disjointed development processes hindering IT agility and degrading ability to meet business demand
  • Inaccurate project forecasts, non-repeatable processes, and rudimentary performance metrics leading to a persistent Business-IT perception gap
  • Perennial tension between management compliance mandates and development approach, which prevents improving app delivery
How do we change development processes, development tooling, and run-time infrastructure to decrease time to market, streamline development processes, deliver on-time and budget, and meet compliance mandates?