This is part 4 in a series on monitoring Kubernetes and Docker. Catch up on parts 1, 2, and 3.
Photo by Nareeta Martin on Unsplash
I have a long list of people I like to blame for the dysfunction I see in organizations. I blame Managers, Directors, CEOs, Testers, Salesmen, Recruiters, Architects, IT Engineers, Customers, Business Analysts, Help Desk, HR, Finance, Consultants, and Coaches.
I blame those with more experience and those just starting. I blame the courageous and the scared. I blame my friends, my foes, and my family. I blame those I understand and those I don’t. I am expert in everyone else’s problems.
Photo credit by Unsplash/Artem Beliaikin
As a Scrum Master, I know that encouraging the development team, product owner, and organization in the adoption of Scrum is anything but not easy. It takes time (a lot of it) and patience.
And during that long journey, it’s vitally important that the Scrum Master never stops improving. In fact, it’s this commitment to continuous learning that helps me perform my responsibilities and enables my team to maximize the values of Scrum.
This is the first installment in a series of blog posts on this topic.
Years have passed since the software world first gasped at the high-velocity achievements of Netflix, Etsy, Flickr, and others, watching in awe as they shipped features in less time than other companies could even begin to start planning them. The secrets to their success were collectively characterized as “DevOps” – a new approach to delivering software that focused intensely on continuous integration, continuous delivery, and breaking down barriers between engineering and operations teams in order to ship faster, and with less risk.
Assertions are an important part of any test automation framework, and Serenity gives us many options. You can, of course, use standard JUnit, Hamcrest or AssertJ assertions at any point in a Screenplay test. But more recent versions of Serenity Screenplay provide an alternative approach, which many developers find easier to use and faster to write: the serenity-ensure module.
Introducing serenity-ensure
The Ensure class produces a Performable, so you can integrate them directly into the attemptsTo() method. It also has a very readable DSL and lets you use code completion to discover the assertions you can use for different values, making writing assertions easier and quicker.
Changing the way we work is extremely difficult . We all know this. It requires us to find novel solutions to wicked challenges, to deal with cultural baggage (i.e. ‘the way we do things here’), and to bring along the people needed to make a change successful. And yet, this difficult challenge is a core responsibility of Scrum Masters.
But how do Scrum Masters and Agile Coaches go about this? What strategies do they use to change the system? Who are their most important allies? And what else can we learn from them?
The real problem is this: Why should you care about how much a delayed release costs you? Maybe you have a “sweet spot” in the way you start your projects or release them. “It just takes that long here.” (That’s the sign of a system impediment.)
Now, let’s try to calculate that cost of delay.
While the main benefits of Agile are higher efficiency and reduced waste of time and resources, shorter delivery time, and more flexibility across the board, there is also one other aspect that requires recognition: It’s the impact that the ability to shorten and flex the development process has on human interactions within the organization.
You may also like: Why Social Situations Exhaust Introverts: A Programmer’s Tale
Because Agile makes it possible for teams to rely on visual communication and tracking more than on in-person data presentation and direct engagement in face-to-face communication, all team members can easily stay informed and engaged in the work, no matter each individual’s comfort level with in-person interaction.
It’s deployment day, and you feel that familiar dread that comes with knowing that your code is going into production. You whisper a silent prayer: “Please God, don’t let my code take down production.” As the servers are restarted you feel the pit in your stomach growing. Beads of sweat roll down your forehead as you watch the logs, check the alarms, and monitor the sales.
If this sounds familiar, you may be working in an environment that practices fear-driven development.
There are two critical factors that need to be present in an enterprise for fear-driven development to take hold.
Welcome to our latest episode of Tom’s Tech Notes! This week, DZone.com’s research analyst Tom Smith chats with Dell Boomi CTO Michael Morton about how to innovate better. Learn who to approach about innovating, how to plan for it, and the importance of not just failing fast, but learning and implementing fast.
And, as always, you can find our podcasts on:
