“Me, and everyone I know who started doing agile, are stressed”. If you ask around, people are feeling a bit more stressed than before the big agile arrived. Why is that, and is good, bad or ugly? Now, where is this stress coming from in agile teams? In the good ol’ days of waterfall, life
Author Archives: Gil Zilberfeld
Last time we talked about the different mechanisms and practices we put in place in order to get us to working software, the main metric in agile delivery. We talked about how “working software” means not just that software is functional, it’s built to last. One of the most effective of these practices is code
“Working software” – How is it made? Here’s the secret sauce – Working software is really about the people who build it. Working software is built by professionals. And professionals are not just tech wizards. They write software in specific effective ways. What practices do we have in our disposal, that make us professional? Think
In a short post, John Cutler reminds us that the work is never done. Customers change, their needs change, we have new ideas, and that’s why we show up for work everyday. His final suggestion is not to be fooled by Jira’s “Done” status. I can’t believe I’m actually defending Jira here, but Done (in
I’ve written a series of posts on integration testing with Spring on “Everyday Unit Testing”. You can find the following: Configurations – How configurations works in Spring (and Spring Boot), not just for integration tests Mocking – How to use different configurations for injecting mocks in integration tests Testing a REST API – How to
We’re going on our family vacation soon, which gives us the opportunity to dabble in all kinds of activities. Including the one starting out with the question: “Are the kids’ passports still valid?”. Nope. And we’re just 3 weeks before the flight. Time to deal with the unexpected. The next day, the kids and I
What happens if we don’t have visibility at the product level? If the organization is just starting out with agile, or not there yet? We’d like to know the status of the whole product, in order to make decisions about the future. When we’re coming up to a checkpoint or review in the project, what
We’ve talked about theory, now let’s see how it’s done in practice. Check out the new post on Everyday Unit Testing. Go on, don’t by shy.
We know that deadlines drive behavior. That’s why in scrum, and other agile methodologies, we timebox the development with those deadlines. They tell us: Focus on the important stuff, and make sure it’s done properly. Since they are good in essence, let’s see how we muck them up. Here’s the process. We prepare for the
Second part of the Leadership resoponsibilities for a better unit testing implementation on Everyday Unit Testing. Check it out. Also, don’t get too close to the cat, it’s on fire.