Case Study: Using Agile

This post describes how we helped one of our clients move from a traditional waterfall development process to agile. Agile was first introduced  into the formal SDLC process in 2010. Starting with the use of Microsoft’s Team Foundation Server, TFS, all of the projects implemented used a hybrid model where the key concept of iterative development was enforced. Iterations were time-boxed in and then reviewed during the retrospective. The end of the iteration required that the application be deployed on its own (through a separate divison) in their own environments. This ensured all aspects of the application were working. This is …

More…

Always Be Releasing

In reviewing older posts, I came across this little gem that hadn’t been posted but is particularly relevant to development today. It’s a short post but hits on a key point for developers and anyone involved in a project that seems to be going on and on: I burn out when I’m not releasing. One of my clients recently started trying some agile practices like iterative development. After doing three three-week iterations, the testing team felt like they needed more opportunity to test within those periods, so we switched to one-week iterations. Ouch — that’s tight and then I re-read …

More…

The Other Shoe…

Ah the joy of watching an end user use your application. Glad to see MS still does it. It’s one of my favorite parts of building applications.   It isn’t just about knowledge transfer from the “guru” to the “learner” – it works the other way too. I got an idea for a new feature in one product after watching my wife, Trish, simply try out a product. All of the assumptions and “learned” behavior go right out the window and instead, you’re left with thinking “how can I make this process easier?” while still “how do I ensure the …

More…

Contact

48 Stonemeadow Drive
Kanata, ON
Canada K2M 2K2

+1 613 851 4496
Contact Us

Connect

Subscribe

Join our email list to receive the latest updates.