Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Mark Levison observed that, after solid classroom training, teams in larger companies still struggle to adopt TDD. To better understand the problem he surveyed team members. In this article he shares the problems he uncovered and his own comprehensive strategy, designed to help anyone introducing TDD into an organization.
We often hear stories about daily standups that have become nothing more than long daily status meetings where team members tune out. What techniques do people have for avoiding this and other standup pitfalls?
Jean Tabaka, Liz Keogh and Eric Willeke got together to contribute something to the "Lean Software and Systems Consortium". Instead they realized the Software Development Community (Lean, Agile, Kanban and well beyond) needed a help remembering the importance and value of true community.
Stabilization sprints are an additional number of sprints added to the end of the normal development cycle before shipping the product. As the name suggests, they’re usually added to shake down the product one last time and drive the last of the bugs. Do they belong in Agile environment or should "Done" be enough.
Unit Testing Time and Dates is an often talked about problem with relatively simple solutions. More difficult is the acceptance/system testing with Time. What strategies are used?
Alan Baljeu was trying to use TDD with his large, legacy C++ code base. He found that the principle of the simplest thing that could possibly work was causing him trouble with the amount of rework.
What is an appropriate Agile Metric? If traditional measures like: Earned Value, Hours Worked, Lines of Code, Code Coverage for Tests are not well suited to Agile Projects, then what is? What rules can we define that will help us choose good Agile metrics?
The sprint is about to finish and you discover that you can't deliver an important story. What do you do? Extend the sprint? Put the story back in the backlog? The team consistently overestimates how much work they can get done in a sprint? What to do?
A month has passed since Agile 2009 and there is now a good variety of feedback on the conference, the sessions and what participants found most valuable.
