Dealing with Troublesome People Have you ever had to contend with a demanding developer? A testy tester? A cantankerous customer? Why oh why do people act that way? Rather than wondering why they act that way, it can be helpful to consider the circumstances that might account for their behavior. |
||
|
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. |
|
Book Review: Continuous Delivery If you didn't already know that the key to reliably deploy quality software is to take a cross-functional, full-lifecycle approach, Jez Humble and David Farley's book "Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation" will help you to understand. |
||
The Potential Pitfall of Ratings Responses to ratings-based surveys are particularly prone to misinterpretation if the surveys don’t allow space for open-ended comments. These comments offer insight into what respondents are really thinking, which may not be obvious from their ratings. |
||
A Psychology Framework That Will Help You Implement CM Practices How does personality impact the implementation of industry Standards and Frameworks? It would seem that following the guidance in the IEEE 828 CM Planning standard is simply a matter of writing CM Plans and documenting your existing CM practices. The fact is that some people implement Standards and Frameworks successfully and others fail miserably. This article presents a popular and highly regarded psychology framework that will help you better understand how to implement Configuration Management. |
||
Dave Thomas - Agile 2010 - The big tar ball and other unintended consequences.
Podcast
Dave Thomas - Agile 2010 - The big tar ball and other unintended consequences. |
||
Boring Triggers Snoring I once attended a presentation by an executive who began by saying, “I want to get through the initial slides so we can get to the interesting stuff.” How would you react to this remark if you were in his audience? |
||
The Shape of Change on Agile Teams Many times, Scrum Masters and agile coaches are confronted with the need to change a team that seems to be stuck in its own behavior. And though team members may be willing to change, they just can’t seem to get out of their current situation. The author sheds a new light on this difficult problem and proposes to change the environment instead of the team. |
||
Becoming Lean – The Why, What and How Although many companies may have heard that the concepts of lean production would be of use to their organization, they do not see how something that sprang from manufacturing practices could apply to software development. This article presents a different way of looking at Lean Software Development—one that is independent of Lean’s manufacturing heritage. |
||
Becoming Lean: The Why, What, and How This article presents a different way of looking at lean software development; one that is independent of lean’s manufacturing heritage. It begins by presenting lean as a collection of a body of knowledge applying lean principles to software development. |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |