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 […]
When transitioning to agile, applying agile methods to a single project is a great way to get started. However, care must be taken to ensure the project you choose is appropriate. Here are five tips to help you pick the right project for your agile pilot. 1. Make sure the project is the right size […]
I’ve talked before about how Selenified supports web services and API testing, and as such, we are constantly working to simplify this experience, and expand out the support. One of the features included in the Selenified 3.0.1 release is the ability to pass in custom headers. Previously, all calls made had the Content-Type set to […]
One of the overarching goals of the Selenified testing framework is to provide testers with a tool that reduces spin-up time on projects and enables them to very quickly get up to speed with writing tests. As such, it was very important that the process of setting it up is just as simplified. For this […]
Q1 2018 came and went quickly this year, and while I scrambled to get many things done, I did at least manage to push out a new version of Selenified! It’s out on GitHub, up in Maven Central, and also, yes, available on our site. We managed to cram in a bunch of updates and […]
