|
How Being Agile Can Maximize Your Return on Investment There is more to calculating ROI than a simple equation. It can be affected by risk, time, and other factors—including whether your team is agile. Releasing software immediately after coding and testing accelerates feedback cycles, minimizes the cost of delay, and increases return on investment. Allan Kelly tells you how.
|
|
|
Do Cross-Functional Teams Mean Cross-Functional People? Managers who want high-performing agile teams may think this involves finding people who all possess every required skill. But in addition to that being unlikely, it would also be a bad idea; it's the mix of perspectives that really gives benefit and value to the business. Instead, find experts in individual skills who can collaborate well together.
|
|
|
Pair Writing across Time and Space Much like in pair programming, working with a partner through pair writing provides increased support and valuable immediate feedback. But there are additional obstacles when you and your partner are not collocated. Here are some tips on how you can still implement pair writing successfully when you can't collaborate in person.
|
|
|
What Improv Can Teach You about Agile Success In both improv and agile, there is a tight-knit community where everyone can explore possibilities and feel free to innovate. Without that community, there can be no trust or collaboration. Travis Klinker tells you how success in both improv and agile means exemplifying transparency, adaptability, and unity.
|
|
|
The Effect of Time on Value in Your Agile Projects Using effort estimates as the only criteria for deciding whether work is undertaken could be leaving money on the table. Considering value—in particular, the effect of time on value, as in whether there is a cost of delay—makes for more intelligent conversations and better decisions.
|
|
|
Using Agile Application Lifecycle Management to Streamline Status Accounting Status accounting is following the evolution of a configuration item through its lifecycle. Using application lifecycle management along with agile helps prevent mistakes, but lets you have the minimum amount of red tape; the team achieves an acceptable velocity without being unduly burdened with too much process.
|
|
|
Simplify Your User Stories: Make Them Independent Writing independent user stories seems simple, but it is actually difficult to do well. There are often parts of some stories that are dependent on other stories' functionalities, so it's not easy to keep them separated. Kris Hatcher relates how his team wrote and scored stories to keep them independent but still meeting acceptance criteria.
|
|
|
Implementing Agile Approaches in the Public Sector In the public sector, a change in standard processes and procedures requires significant effort and, often, approval from external vendors and elected officials as well as internal stakeholders. To get buy-in to become agile, you have to utilize all Scrum tools at your disposal to show the value of the proposed agile process.
|
|
|
Understanding Culture and Agile Application Lifecycle Management While the technical complexity of real-world ALM may be substantial, sometimes the people issues present even more complex challenges. Being able to understand the personalities and work culture of the folks doing the work can help you implement ALM in a comprehensive and effective way.
|
|
|
Estimating Business Value in the Shark Tank You can use analytical methods to assign business value to a user story, of course, but another way is simple estimation. Allan Kelly describes an estimation exercise that combines the Scrum tool of planning poker with a TV show format to add some fun. You end up with enlightening conversation and revealed requirements.
|
|