|
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.
|
|
|
Business and Development: Working Together to Build Better Products Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.
|
|
|
Strategies for Encouraging and Facilitating Team Feedback Sessions We know the importance of quick feedback cycles in our builds so we can fail fast and get reactions from the end-user. But sometimes agile teams forget the importance of gathering responses from other team members. This article details several methods for eliciting feedback, as well as how to pick what's right for your team.
|
|
|
Plotting Data to Understand Your Agility Many teams think they are agile in their projects, but if you're not receiving and analyzing feedback regularly, you're not really agile. Plotting the feedback you get on a chart throughout your sprints can help you see whether you have a lag. Read on to learn how to gather and use your feedback to be truly agile.
|
|
|
Would Santa Claus Make a Good Product Owner? The elves working on Project Santa—you know, the big delivery that happens every December 24—have decided to go agile. But Santa, the product owner, is busy and not always available to answer questions or provide guidance. What kind of suggestions and improvements should they address in their retrospective?
|
|
|
Who Is the Real Product Owner? Communication is always vital on an agile project to ensure everyone is on the same page, but it's perhaps most important in a relationship between a vendor and a customer. Here, Marcus Blankenship relates a personal story about a project where communication failed, and gives some good tips for how to avoid it happening to you.
|
|