This SecureCI release was mainly about modernizing our infrastructure as code, our release process, and automating manual steps to set us up for quicker releases in the future. It was a very long and painful process, but finally, an updated version of SecureCI™ is available! So, what can you expect from this release? New Features First […]
DevOps means different things to different people. To me, it is a culture of communication and collaboration across the entire team. In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to give us confidence that we are producing a viable candidate for production, so we have […]
Many are beating the drum that DevOps is something new and different—just like agile was new and different before it. Make no mistake, DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto, and one could argue that DevOps […]
2018 keeps moving along whether we are prepared for it or not. Now that it’s halfway over, you have another Selenified release to enjoy! The not so long awaited 3.0.2 release is out! It’s out on GitHub, up in Maven Central, and also, yes, available on our site. We fixed a few bugs and updated […]
Successful agile teams often have a coach driving continuous improvement. While some coaches are effective initially, many eventually succumb to pitfalls that inhibit their team’s growth and fail to compel any lasting changes. Here are five common pitfalls of agile coaches I see in most projects that fail to improve. 1. Not Applying Agile to […]
It seems like every other day, someone in the software development community feels the necessity to declare that agile is dead and they have something new and better. Sometimes it’s one of the founders of agile who now think the Agile Manifesto is dated and needs to be overhauled. Other times it’s ageless software veterans […]
A key part of an agile process is the retrospective. The purpose of retrospectives is to identify where you can improve and reinforce what you are doing well as a team. They typically happen at the end of each sprint in Scrum, at regular intervals in kanban, or after something goes wrong in your organization. […]
Many are beating the drum that DevOps is something new and different—just like agile was new and different before it. Make no mistake, DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto, and one could argue that DevOps […]
Long gone are the days of waterfall software development. The agile movement has brought common-sense software development principles to nearly every corner of the world and changed the way we look at software. This philosophy left marks on how we look at our infrastructure, too. With agile came DevOps and the idea to bring together […]
The Agile Manifesto states that “at regular intervals, the team reflects on how to become more effective, then tunes and adjust its behavior accordingly.” Despite being a key principle of the manifesto, continuous improvement eludes some organizations. They find themselves “doing agile” instead of “being agile.” In traditional agile approaches, the sprint retrospective provides a […]
