Agile Methodology

  Able to move quickly and easily; well-coordinated

• Agile enterprise :

– A fast moving, flexible and robust company capable of rapid response

to unexpected challenges, events and opportunities

• Agile software development :

– A group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross functional teams

Agile software development methods deliver working software in smaller and more frequent increments.

What does it take to  "Be Agile" :

• Be customer-centric

• Be lean

• Be collaborative

• Be communicative

• Be adaptive

• Be measurable

• Be consistent

• Be results-oriented

• Be reflective

It is more important to “be agile” than to “do agile.”

DevOps increases agility by

• Breaking down silos

• Improving constraints

• Applying agile principles to both Dev and Ops

• Sharing knowledge,skills,experience and data

• Recognizing the criticality of automation

• Deploying faster with fewer errors

DevOps extends agile principles beyond the boundaries of the software to the entire delivered service.

Agile Service Management (Agile SM) ensures that ITSM processes reflect Agile values and are designed with “just enough” control and structure in order to effectively and efficiently deliver services that facilitate customer outcomes when and how they are needed.

– Adapts Agile practices to ITSM process design

– Implements service management in small, integrated increments

– Ensures ITSM processes reflect Agile values from initial design through CSI

– Encourages “minimum viable” and “just enough” processes to increase speed and conformance

Agile Service Management does not reinvent ITSM – it modernizes the approach.

Scrum is

– The most commonly applied Agile software development practice

– Deceptively simple yet difficult to master

Scrum increases the ability to release more frequently.

Learn more about the Scrum here :

Scrum Agile

The Scaled Agile Framework (SAFE) is

- a proven, publicly available framework for applying Lean-Agile principles and practices at enterprise scale.

- Integrates Lean and Agile thinking into software development

• Focuses on iterative and incremental development, agile SW development, product development flow, lean thinking and field experience at enterprise scale

• Can be applied to organizations with a large number of practitioners and teams.

SAFe

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more