![]() |
Two Measures of Development Effectiveness: Predictability and Optimization Nearly every CIO or VP of R&D is struggling to improve their time to market while increase the number of features delivered within stagnant or shrinking budgets. Two objectives of software development teams will address this need are to improve predictability and optimize productivity By combining views of predictability and productivity of the development activity, the team and its stakeholders can quickly and easily tell if the development is on track, if predictability is improving, and if team members are self-aware enough to improve their overall output. |
|
![]() |
Behavior Unbecoming of a Leader One of the most important roles of a leader is to serve as a role model for others in the organization. In this article, Naomi Karten describes a situation in which a CIO forgot this responsibility, almost taking action that would have undermined his efforts to reverse the IT organization’s plunging morale. |
|
![]() |
Stop the Wishful Thinking: Software Estimation Reality Check Daryl Kulak tackles the most common beliefs in software development regarding estimating, and shows us ways and methods to help developers deal with the demands of businesspeople. |
|
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. |
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 |