The Latest
|
The Three Amigos: All for One and One for All[magazine] Analysts determine what needs to be created. Programmers create it. Testers find the holes in the work of both. That's one way to do it, but all three can collaborate to do these things better, and more easily, too. |
||
|
Updated Agile Program Management Slides Posted[article] 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?[article] 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[article] 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. |
||
|
10 Thoughts On Technical Debt[magazine] Many people realize that the technical debt spiral is a perverse incentive—it ends up rewarding behaviors we don't want and causing long-term pain. In this article, Matt Heusser moves beyond cliché to talk about how tech debt happens and what we can do about it. |
||
 |
Book Reviews for BAs[magazine] Get a head start on your New Year's resolution. Hone your business analysis skills or learn new ones, and make 2012 the highlight of your career. |
|
|
Tips and Advice: Test-Driven Development—Bob Payne and George Dinwiddie[article]
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[article]
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[article] 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. |
||
|
Improving QA-Development Communication: An Interview with Amit Chopra[interview] In this Sticky ToolLook interview, Microsoft senior program manager Amit Chopra takes a look at some of the common communication breakdowns between QA and development teams and offers suggestions for avoiding or repairing those situations. |
||
|
Estimating the Unknown: Dates or Budgets, Part 5[article] 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[article] 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[article] 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[article] 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?” |
|
|
Is It Beautiful?—Aesthetics in Software Testing[article] With all the faces it presents, surely software can be said to possess or lack beauty. But, what does it mean to have beautiful software, and how do we evaluate it? In this installment of his series on philosophy and testing, Rick Scott takes a closer look at software aesthetics. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.