Skip to main content

Golden Keys to Unlock Agile Success

Communication and Education before Collaboration 

An engineer attending a recent DevOps FND class for certification said “OMGosh! I have been trying to do DevOps and I really did not understand what it really was!” He knew that a self-organizing team was defined as a group of motivated individuals who work together toward a goal, have the authority to take decisions and readily adapt to changing demands. Solutions are derived from inter team collaboration. Innovation is the name of the game for digital transformations. All true but … “authority” without ability is dangerous. 

Let’s not forget that before these teams are able to recommend innovative ideas for improvement that we must communicate the strategy and outcomes that deliver value. Also true is the fact that we must educate teams to continuously enhance their skills. 

Challenge: During your next virtual or face to face meeting with staff, ask a few questions to validate that all are on the same page. You could ask “What is Agile?”, “What is DevOps?”, or a real good one is “What is the difference between Continuous Delivery and Continuous Deployment?” One approach is to pass around sticky notes to the group and ask them to put their answer to the one question you give them onto the note. Pick a question that is relevant to your transformation. If you have 10 people in the room and you get 10 different answers, this is a good indicator that some communication and education is necessary. Without the communication and education collaborative teams may not have the ability to innovate at the speed of need and ideas may be subjective. Results, “The way we have always done this”. Lack of education is high risk. 

Focus on the Value Stream 

Certified Agile Service Managers take Agile beyond development because they know that Agile Service Management requires the entire value stream to be Agile. Example: If a change request takes a week to authorize mid-stream in the delivery pipeline, what did you gain from the speed for which the developers and engineers were able to produce? You cannot silo Agile. The value stream for delivery of a product or service includes all stakeholders and activities from idea to delivery of value. Value is a means of delivering a service by facilitating the agreed upon outcomes that are agreed to with our customers. The value stream in its entirety must produce at the velocity of business cadence. DevOps does not stand alone. AGILE, ITSM and LEAN along with other methods and principles are like tools in a tool box. Don’t limit what you can achieve by limiting your tools. Aim high for fast resilient delivery of value. 

For more information: 




Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…