Updated Agile Program Management Slides Posted I missed one presentation in my last post. At Oredev, I had an opportunity to speak with the PMI Sweden folks (at least, the southern Sweden folks). I talked about Agile Program Management, and discussed my current thinking about agile program management. |
||
Who Defines “Success” for Your Project? An otherwise good project management book provokes Payson with definition of “success” that rubs him the wrong way. In this article, he presents his case. |
||
Tester, Know Your Product Should you diligently produce multiple big documents before testing begins? Consultant Fiona Charles argues that you should do that only if you believe that documentation is your product as a tester. If your product is information, you should instead minimize test documentation and engage with the software to build the product your stakeholders are paying for. |
||
Tips and Advice: Test-Driven Development—Bob Payne and George Dinwiddie
Podcast
George and Bob Payne discuss one of the most beneficial and underutilized agile technique, test-driven development. The data is in, and you need to be doing this if you want to call yourself an agile engineer. |
||
ADP West 2011: Ken Pugh—Acceptance Test-Driven Development
Podcast
Ken and Bob Payne talk about Ken's book on acceptance test-driven development. This is a topic that has been gaining a lot of traction in agile teams. Acceptance test-driven development is a technique that some teams are using to improve quality and collaboration between business, testing, and development. |
||
Make an Attitude Investment Whether you’re concerned about your day-to-day work or the long-term goals you’ve set, a good attitude can make all the difference. In this article, Laura Brandenburg expands on some tips gathered from Jeffrey Gitomer’s Little Gold Book of Yes! Attitude. |
||
Estimating the Unknown: Dates or Budgets, Part 5 In many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost. |
||
From One Expert to Another: Meeta Prakash Meeta Prakash has been involved in testing for twelve years. In this installment of the From One Expert to Another interview series, Anne-Marie Charrette speaks with her about her testing experience, coaching, and the importance of understanding the different cultures with which you engage. |
||
Helping the Customer Stick to the Purpose of a User Story Lisa Crispin writes that you need to understand the purpose of a user story or feature. Start with the "why." You can worry later about the "how." The customers get to decide on the business value to be delivered. They generally aren't qualified to dictate the technical implementation of that functionality. It's up to the technical team to decide the best way to deliver the desired feature through the software. |
||
![]() |
Estimating the Unknown: Dates or Budgets, Part 1 Almost every manager I know wants to know when a project will be done. Some managers decree when a project will be done. Some managers think they can decree both the date and the feature set. There is one other tiny small subset, those managers who ask, “When can you finish this set of ranked features?” |
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 |