![]() |
Specification by Example: Collaborating on a Scope without High-Level Control Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project. |
|
Leadership, Management, Transitioning to Agile Johanna Rothman has worked with several management teams who want her to train them or their project managers to take over the agile training. While on the surface this doesn't seem an unreasonable request, when one considers the self-managing, self-organizing nature of an agile team, the incongruity of this thinking begins to shine through. |
||
![]() |
How to Give an Accurate Answer Scott Ames explains the Test Requirements Agile Metric and offers a real-world example of its use in software estimation. |
|
![]() |
Story Mapping the Wrong Way When Lisa Crispin’s team got an opportunity to put the story mapping ideas she picked up from Jeff Patton into practice, they excitedly rushed into it and missed a few steps. Find out what happened, what didn't happen, and what they learned from it all. |
|
Questioning before Answering The other day I came across a short video in which a parent is faced with answering a unexpected question posed by her young child. I found this video amusing because, being the parent of a kindergartener, I expect to be faced with many awkward moments like this in the future. I also found it an interesting metaphor for software requirements gathering. |
||
Agile Requirements Management with Keith Johnson Keith Johnson is vice president of product development at Jama Software. in this Sticky ToolLook interview, he discusses some of the changes that agile development has brought to the requirements management process. |
TechWell Staff
December 7, 2011 |
|
The Two Metrics that Matter This article is designed to provide specific steps for understanding your development effectiveness. Getting this right will help move your software development group toward being a true business partner, if it is not already. |
||
![]() |
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. |
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 |