Yeah, we want to do DevOps. We understand this is a critical thing, it is important for succeeding in our Dev- and Ops-projects. We can’t do without.
…we need to get the whole picture first. We need to have a fully featured DevOps-concept. We need some infrastructure. We need top clarify with our Stakeholders.
You know what?
These are only excuses for not doing DevOps.
The best approach to DevOps is by simply starting it. Forget about that fully featured DevOps-concept to be discussed throughout all hierarchy levels of your organization. Forget about providing the perfect infrastructure. Forget about everything – just start it!
DevOps is a process and a mindset. It is an approach to collaboration, to transparency and to knowledge sharing. Yes, it always can be done better, more aligned, deeper integrated, etc.
But nonetheless: The best way to start doing DevOps is to simply start doing it.
I’ve never seen a team being that committed. That focused. That inquisitive. That eager to learn. That funny. That great.
Team, I am so proud of working with you!
Next week, we will start our expansion. I mean: We will really start it. Three new Team-Members at the beginning of the month. Two more in the middle. One more beginning of August. One more at mid of August. One, two, three perhaps beginning of September.
But: I am not afraid. I know, that we already have a great team and we will continue to be one. We looked carefully at the new colleagues‘ character and found them to match the team in culture and commitment.
Sandra, Ronny, Emily: Welcome!
You will be part of Cloudibility, you will shape us and you will grow with us. And I am very confident to count you in next time when I write about the:
This has been said just seconds ago in a meeting I am currently attending. We’re not talking about freelancers here, but a pseudo-agile project with an enterprise customer.
See the problem?
Agility is not about having meetings cluttered all over the day, but efficiency. If your calendar is blocked so extensively by meetings, then perhaps, perhaps something is wrong.
Pro-Tipp: Change it. Cancel the unnecessary or unproductive meetings. Only attend meetings making any sense. Do not attend meetings for the sake of attending them.
Pro-Tipp 2: Participating in Scrum? Only do the scrum-stuff: Daily, Retrospective, Review, Plannings and perhaps Estimation meetings. All the other meetings should be obsolete if you communicate transparently. They should be attended by some POs or Architects, but not by every other person participating in the team.
Pro-Tipp 3: Participating in Kanban? Only do the minimally required stuff: Daily, Jour-Fixes or Reviews, Plannings. Work with your kanban board. All the other meetings should be obsolete if you communicate transparently. They should be attended by some POs or Architects, but not by every other person participating in the team.
(Hmmm, that’s pretty much the same content in Tipps 2 and 3. Coincidence? I don’t think so…)
Agility is gorgeous. Unless you’re in a project, where agility is mistaken by spontaneity or talkativeness. Or worst case: All together.
Just today, I was sitting for three hours in several daily calls for different aspects of a project. So much redundancy there, and Scrum Masters which try to insist on rules instead of pragmatic approaches.
Agility to death. Without any sense. And without any productivity.
Cloudibility is not even a year of age, but we already need an organizational diagram, since we are already close to 20 persons (17 beginning of September) working with and for us – and this is only the number of employees which have already signed their contracts, not to be spoken of the ones we are currently having conversations with!
We take this very seriously since Michael and I have experiences in enterprise environments as well as a startup history. For us, one very deciding aspect for the success of a company is the organizational structure – if you don’t have it, you are very likely to fail. And having a structure and an internal organization frees the „creatives“ from having to care about everything, ultimately allowing them to focus on their work and the excellence in their doing.
One final note: The importance of a working organization and a working back-office cannot be overemphasized. That’s why I am so happy with our COO Claudia, Linda, the whole team and their invaluable work.
Today, we decided to grant every employee of Cloudibility up to five additional vacation days in two years. Only condition: The management needs to agree on this and in order to agree, the employee needs to agree to produce some output within these additional vacation days which we (Cloudibility) can use in our marketing or publications.
Such an output could be some photos containing the employee wearing some Cloudibility Shirt and – say – the Colosseum in Rome or some employees running atop the Great Chinese Wall or a Publication. We don’t impose any limits here, as long as we can use it in the end.
So, Cloudibility Employees: Surprise us! Get creative! Go, have some fun!
Below are the slides of my presentation at #ContainerDays 2018 in Hamburg. I spoke about the bigger picture regarding CloudNative Applications – i.e. #DevOps, #Crossfunctional #Collaboration, #IaaS, #SaaS, #PaaS and the change of #Mindset required for utilizing all the advantages of #Cloud environments.