Over a million developers have joined DZone.

The Best of the Week (Mar. 22-29): Agile Zone

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

In case you missed them, here are the top posts from the Agile Zone this week--as chosen by yours truly. This week: There's just no time to learn, answering the question "when will we complete our agile transformation?", Choosing software by what's best for the business, building a "hat rack" for open source contributors, and how to fire employees (don't!).

1. No Time to Learn

To a large degree, Agile software development IS learning. We try things mindfully, watch the results we get, reflect on why we get those results, and adjust. We do that at multiple levels of granularity, from choosing what products to develop to writing code that works reliably. There is always more to learn. There are ways to learn better ways to learn. 

2. When Will We Complete Our Agile Transformation?

People tend to ask me the general question of how long it will take to complete an Agile transformation. In order for change to occur in your organization, you must enable it to happen. Want to know how long it will take to complete an Agile Transformation? I think you need to listen to your guide but you also need to control the weather.

3. On Choosing Software by "What is Best for the Business"

When people are discussing what language/framework/library to use for something, the general criteria people talk about is “what best solves the business problem.” It’s much more honest to just admit that technology choices are made from a desire to work with a new technology, or because a technology is familiar.

4. Let's all Build a Hat Rack

Open Source contributions are often anonymous and the rewards are intangible. A little bit of tangibility is a huge thing. There are unsung heroes at every hackathon and tech meetup who could benefit from some recognition. Perhaps they're looking for a new job or a transition in their existing job. Perhaps they're looking to break through one of the obscure social barriers that seem to appear in a community where everyone looks alike.

5. How To Fire Employees

Don’t. There, that was an interesting post. Short, but interesting. When you worry about how you’ll fire people, what you really should be worried about is why you need to fire people in the first place.

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.


The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}