|
Agile Customer Validation Vision When applying validation, should you limit yourself to the end-of-sprint review or demo—the practice most people associate with agile validation—or should you utilize other validation types where customers provide feedback? Where do the customers who attend validation sessions come from? In this article, you will learn about the importance of the ACVV and how to establish a vision to benefit the product and each project therein. |
||
 |
We're Agile I always recommend to teams newly transitioning to agile that they keep every iteration the same length. This helps them learn to manage their time, and after a few iterations they'll start to get a rhythm. Hopefully, they'll learn to work incrementally, doing testing and coding concurrently as part of one development effort, so that user stories are finished throughout the iteration, and testing isn't pushed to the last day. |
|
|
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. |
||
|
ADPWest 2011 - Michael Spayd and Lyssa Adkins - Agile Coaching Institute
Podcast
Bob speaks with Michael Spayd and Lyssa Adkins about the Agile Coaching Institute at ADPWest 2011. |
||
|
ADPWest 2011 - Drew Thoeni - Techwell and the ADP/Better Software Conferences
Podcast
Bob speaks with Drew Theoni about StickyMinds.com TechWell.com and Agile Development Practices West conference. |
||
|
Simulation Games: A Way to Improve Communication in the Team One of the hardest daily tasks developers, QA, ScrumMasters, and product owners encounter is effective communication with others. Sound implausible? According to many articles, research, and personal observations, the main cause of project failure is not technology or hardware, but inefficient communication stemming from lack of effective communication between team members, incomplete business analysis, imprecise requirements, and vaguely formulated business objectives. |
||
|
Tips and Advice - Acceptance Test Driven Development and the 3 Amigos Process
Podcast
Bob speaks with George Dinwiddie about acceptance test-driven development and the Three Amigos process. |
||
 |
Four Agile Tips to Eliminate Rework in Application Development Your applications need to meet business needs, overcome complex processes, and provide instant results to customers. And, ideally, they’ll require minimal rework on your part. The first step to success is requirements definition. Here, Filip Szymanski offers some tips from agile methods that will improve your requirements—even if you haven’t otherwise adopted agile. |
|
|
How Do I Write Requirements Using Stories and Acceptance Criteria?—Part Two Russell Pannone and Geoffrey Bourne write that at first glance, a User Story looks simple, almost trivial. However, it contains the essence of the project deliverables. It describes the who, the what, and the why of every piece of delivered functionality. |
||
|
For Project Managers, Agile Is About Asking a Different Question Daryl Kulak explains that if we don't ask the right question at the beginning of the project, then no matter how well we answer, it won't be helpful. Perhaps the biggest difference between agile and waterfall is the question being asked. The scope of the project and any judgments of progress are related to this very fundamental question. |
Pages
Upcoming Events
| Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
| Jun 08 |
AI Con USA An Intelligence-Driven Future |
| Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |
