|
A Case Study in Implementing Agile This case study serves as an example of how adopting agile can be extremely beneficial to an organization, as long as situational factors are considered. Adopting a new development method is a strategic, long-term investment rather than a quick fix. As this article shows, making deliberate, fully formed decisions will ultimately lead to better outcomes.
|
|
|
What the World Cup and Agile Development Have in Common There are a surprising number of similarities between successful World Cup and agile teams. Both must be diligent in four areas in order to reach their “goals.” This article explores the parallels between the two for selecting the team, getting up to speed, consistency, and game plans.
|
|
|
Avoiding the Organizational Death Spiral The death spiral supersedes the death march in that the death march is a singular event, whereas the death spiral is systemic. It is the result of organizational dysfunction where teams march toward deadline after deadline without reflecting on or questioning if there is a better way to deliver software. There is! Take these positive steps.
|
|
|
How Agile Is Growing as It Goes into Its Teenage Years Agile is growing up and is now officially a teenager. It has moved from being a somewhat rumbustious child with some overzealous followers and a skeptical management crowd to something that is generally accepted by the mainstream IT community and particular management. Has the agile community lost something? Are the founding members and early practitioners evolving the practice? Is this good? Well, the answers are yes, yes, and maybe.
|
|
|
Load Test Your Website Before Your Customers Do When you release a website or web application, it’s going to face a lot of very public load testing. If it performs poorly, there’s a good chance that you’re going to lose a lot of customers. Colin Mason offers some tips for load testing in order to ensure a better customer experience.
|
|
|
It’s the Goal, Not the Role: The Value of Business Analysis in Scrum “Business analyst” is not a distinct role on Scrum or other agile teams. And yet, the goal for the team—to deliver high-valued product needs—requires strong business analysis skills. Ellen Gottesdiener and Mary Gorman describe the vital analysis work needed reach the goal, regardless of role.
|
|
|
Harvesting Stakeholder Perspectives to Organize Your Backlog When Mary Gorman and Ellen Gottesdiener facilitated a game called The Backlog Is in the Eye of the Beholder for the Boston chapter of the International Institute of Business Analysis, both the players and the facilitators learned some important lessons in organizing a project requirements backlog. In this article, they describe the game and what it revealed, including the value of truly knowing your stakeholders.
|
|
|
An Agile Approach to Scheduling When we schedule too many variables, things start to slip and soon the schedule is out the window. Paying attention to your project's constraints can help you set realistic scheduling goals that you will actually be able to stick to.
|
|
|
Why Agile Development Teams Need Business Analysts Unfortunately for the business analyst (BA), much of the literature regarding agile development focuses on the perspective of the developer, largely ignoring the role of the business analyst. BAs play a key role capturing requirements on large, software-intensive projects. Teams are co-located where programmers and their "customers" interact directly as a means of eliciting requirements. Organizations that are moving toward agile development may wonder if a has a role in agile software development. The answer, as addressed by this paper, is a resounding "Yes."
|
|