DevOps Check-up proposed by Kiratech (www.kiratech.it) consists of 6 man-days of consultancy with our DevOps specialists:
- 2 preparation man-days
- 2 delivery man-days
- 2 report preparation, drafting and discussion man-days. The report will be provided by two weeks from the delivery days.
Below you can find all the information for the best execution of our consultation, from the consultation days to preliminary work, in order to prepare the audience on the topics that will be addressed.

Agenda
Delivery days aim to define more precisely the objectives that the consultancy wants to reach, which are the success criteria that will qualify the results achieved and which are the criticalities and risk factors that should be considered.
Some of the emerged critical points will be further investigated, or, if the situation will be sufficiently clear, we will proceed with a status report and a debriefing with the participating stakeholders, to define the order of priority in the subsequent activities.
Kiratech’s consultants will facilitate the discussion on these topics and participant stakeholders will briefly present their role in the company (3-5 minutes) and how their area (or projects and activities) is involved in the software development process (from design to analysis, development, production, management and everything related to DevOps, at all levels). For example:
• process automation management, which is the approach called Infrastructure as Code;
• monitoring;
• approach based on continuous integration and continuous deployment;
• microservices architectures;
• transition to cloud native or cloud first systems.
Based on the outcomes, we will decide on which aspects we will focus further to clarify all the implications and to clearly identify the value (and its priority) that we will deliver to the company. At this stage it’s usually necessary to go in depth with the company business model and products, so it’s fundamental to have among the participants an audience that is representative of multiple company departments.
Reports
At the end of the engagement, reports will be created.
The main report, which will be produced during the analysis and summary sessions, is a profile of the use of the platform and the tools that the company provides. From this report will emerge the user stories and the daily activities required to produce and manage the software created by the company: it is usually a draft made of post-it on a blackboard.
A short paper with a draft of the next activities, it is needed for the real report – a minute of the day.
A report related to the DevOps Check-up.
Room organization
To carry out consultancy activities in the best way, we recommend some adjustments:
- a private meeting room;
- a blackboard to take notes and post-its;
- a projector with VGA / HDMI output.

Usually after two weeks, we will produce a technical report.
Summary report on the outcome of the DevOps Check-up
The summary report on the outcome of the DevOps Check-up contains the elements to set the subsequent definition of DevOps Strategy or, in general, to approach the topics related to software production and management.
The report contains:
- an introduction of what has been done;
- the actual situation of the customer, with particular focus on the type of processes analyzed; critical results emerged (which could be related to a large number of issues, related to tools and practices, to processes and working methods);
- proposals for improvement and an action plan;
- the times and costs for the next activities or targeted interventions.