Section » Best Practice
The Challenges of Release Management (Part 1 – The Basics)
Often we focus on the requirements, construction, and test aspects of software development without perhaps enough regard for the deployment or release efforts. But depending on the nature of your application, these considerations can be as complex as the development itself. Release management is generally not just a technical effort. It often includes
More Articles
Now hiring our next great ALM Consultant!
Northwest Cadence is growing our team and looking for a great ALM Consultant. Something you are interested in pursuing or know someone who should? Please send any inquiries and resumes to careers@nwcadence.com. At Northwest Cadence, we have created a work environment that emphasizes excellence, integrity,
TechEd 2009: We’re #2 (And #3, and #4)
We’re all finally home! Jeff Levinson, Shad Timm, and I spent last week speaking, listening, learning and playing at TechEd 2009 in Los Angeles, CA. Those who’ve been to TechEd, know the fire hose of information unleashed at the attendees coving developer topics from designing Azure cloud based
We’re Speaking At Tech Ed!
Both Steven Borg and I will be speaking for a combined total of 4 sessions and 1 pre-con. The pre-con session is PRC05: Improve Your Software Development: Real World Solutions with Team System 2008. We’ll be discussing solutions that our customers
Northwest Cadence Attains Gold Certified Partner Status in Microsoft Partner Program
Northwest Cadence Further Distinguishes Itself by Earning a Microsoft Competency in Custom Development Solutions and Learning Solutions Kirkland, WA, USA – 9 January, 2009 Northwest Cadence, www.nwcadence.com, today announced
Practical Process Improvement (Part 4)
In the previous two posts (Part 2 and Part 3) I covered an ideal bug process and the metrics
Practical Process Improvement (Part 3)
In the last post in this series I discussed the process involved around the first part of the ideal bug process. In this post I will finish up the rest of the process and metrics for handling bugs. Fixed,
Practical Process Improvement (Part 2)
In my last post I talked about why metrics are important and what the goals are in using metrics. In this post I’ll talk about the bug process. How does your team handle bugs, how can you gather metrics on
Practical Process Improvement (Part 1)
So, its been a while since I regularly posted but starting every week or two weeks I’ll be posting a bit on the topic of Process Improvement. Not from a high on the pulpit position but from the “how do I figure out what my problem is and, and more importantly, how do I solve it.”
Branching Strategies
I hope everyone had a happy new year and a safe holiday season. Now that I’m done with beginning of the year housekeeping I’m back to blogging. This is the second in a series of posts on branching strategies. Branch by Quality is the most complex and flexible branching strategy so this strategy
Branching Strategies
Any and all comments are welcome regarding this series of posts (okay, you can comment on other posts too). We woul appreciate any feedback pointing out alternatives to these strategies, whether they helped you or not and maybe your experiences dealing with branching strategies. This series of posts
How many Team Build types should I have for one solution?
How many Team Build scripts should you create? Basically, you should create one build script for each and every way you’d like to report on your data. For instance, you should have a build script for your Continuous Integration (CI) build, one for your daily build, one for a weekly build, and