The main purpose of the Daily Scrum is for team members to make and follow-up on commitments to one another that work towards the team’s shared sprint commitment. If your Daily Scrum has become unfocused, too long, or otherwise ineffective, here are seven ways to get it back on
In my previous posts on WatiN, I lamented the shortage of online documentation and resolved to do something about it by documenting the patterns I’ve found for good WatiN tests. This is the first in a Read More
At my current client, we’ve decided to use WatiN, largely for the C# vs. Ruby reason I discussed earlier this week. After spending a week working with WatiN (following a year of rarely using it), I’m impressed. Ruby and the active Watir community still have their advantages. But WatiN has really come into
Bob Hartman and I are offering an Agile Product Management Boot Camp course March 9-10 in Denver. If you’re a product manager, product owner, business analyst or in any other product facing role in an agile (or soon-to-be agile) environment, this intense, hands-on course is a great opportunity for you to ensure that you’re helping
I’ve noticed a pattern with several of my .NET clients who want to get into automated acceptance testing for web applications. They like the idea of WatiN because it would let them write tests in the same language as their production code. But then they notice that there’s much more documentation and apparently a
Denver’s new APLN chapter is having our first proper (i.e. non-planning) meeting next Tuesday.
Date: January 20, 2009
Location: Sigis Cabaret room in the Tivoli Student Center on the Auraria Campus
Our topic will be an open discussion on how to convince management that agile is the proper approach
I’ve decided to experiment with Twitter as a way to post more often than the once or twice a week I do here and to engage in conversations I’m otherwise missing. Follow me here: http://twitter.com/rslawrence.
Anyone else on Twitter? Have you found it