Join us for the What’s New in Seapine ALM 2012 webinar on February 7th as we showcase over 100 new features and enhancements for Seapine ALM 2012. The improvements to Seapine ALM 2012, which includes TestTrack, Surround SCM, and QA Wizard Pro, aim to help you deliver quality software faster.

New TestTrack features include a new native relational database, custom fields that calculate values, and draft and active custom fields. Surround SCM’s new features include improved offline support, more flexible mainline branches, and additional integrations, while QA Wizard Pro now features stress testing, Google Chrome support, integration enhancements, and more.

In the one-hour webinar, Paula Rome and Grant Lammi, Seapine product managers, will demonstrate the new features in Seapine ALM 2012. When the demonstration is over, you’ll have time to ask questions and learn more.

The webinar is being offered twice to accommodate Europe and North America attendees. The first webinar begins at 2:00 p.m. Western European Time (9:00 a.m. Eastern Standard Time), and the second will follow at 2:00 p.m. Eastern Standard Time (11:00 a.m. Pacific Standard Time).

Join us!

Thanks to everyone who joined us for our Scaling Agile for Project Teams webinar. The recording is now available on YouTube if you missed the webinar or want to watch it again. Q&A from the session follows.

In a 2010 study, Forrester Research reported that roughly 88% of respondents had more than 10 members on a team. And, only 17% had the entire team co-located at the company headquarters. Join us for this 60-minute Agile XXL: Scaling Agile for Project Teams webinar on Wednesday, November 9, at 2:00 p.m. EST (North America), to learn more about scaling Agile. Alan Bustamante, senior Agile consultant, will discuss the people, process, and tools—what he calls “project support pillars”—that must be in harmony before you can successfully scale an enterprise Agile team. He’ll also share common challenges in solidifying each of those pillars, and early warning signs that a project team is at risk of serious issues as it scales.

You’ll learn:

• A model for understanding what happens when people, process, and tools are not aligned.
• Common problems faced by organizations struggling with scaling Agile teams.
• Proven solutions to mitigate the risk associated with scaling Agile project teams.

Register today and learn how to scale your Agile project team regardless of team size or team location.

Thanks to everyone who joined us for our Automating Traceability and Documentation webinar. The recording is now available on YouTube if you missed the webinar or want to watch it again. Q&A from the session follows.

Global Team

On November 9, I’ll be hosting the Agile XXL: Scaling Agile for Project Teams webinar. I haven’t ironed out the details of this webinar yet, but thought it would be good to write a primer for the event.  While I have been practicing many Agile techniques on large, distributed projects since 2002, I didn’t start formally putting them together as a collection of practices in the form of Agile projects until 2007.  It was in 2007 that I say my Agile journey and passion for Agile software development officially began. Since then, helping organizations adopt Agile practices for large and/or distributed project teams has been of particular interest to me because most of my clients have fit into the category. Let’s take a look at some numbers.

Continue reading…

Thanks to everyone who joined us for the Requirements and Agile: Keeping up with Change webinar. If you missed the event, take some time to watch the Requirements and Agile: Keeping up with Change recorded webinar. Attendees asked several interesting questions, all of which we weren’t able to address during the webinar. To follow up, and invite others to participate, we’ve included the Q&A below.

Continue reading…

Requirements or user stories? Why not both? Attend our Requirements and Agile: Keeping up with Change webinar on October 4, at 1 p.m., to learn how to minimize gaps in verification and validation practices sometimes seen when using Agile methodologies. These gaps are typically a result of moving away from formal requirements in favor of user stories, which are quicker to develop but typically not as rigorously defined.  Continue reading…

Thanks to everyone who joined us for the Measuring Technical Debt with Load Testing webinar. If you missed the event, take some time to watch the Measuring Technical Debt with Load Testing recorded webinar. Attendees asked several interesting questions, all of which we weren’t able to address during the webinar. To follow up, and invite others to participate, we’ve included a complete Q&A below.

Thanks to everyone who joined us for the final webinar our TDD 101 Learning Series. If you missed the event, take about 30 minutes to watch the Beginning Test-Driven Development in a Legacy System recorded webinar.

If you missed either of the prior webinars, or want to brush up on your knowledge of test-driven development, browse to Learn Test-Driven Development at TDD 101.

Thanks to everyone who joined us for the second event in our TDD 101 Learning Series. If you missed the event, take about 25 minutes to watch the Writing Good Unit Tests recorded webinar. Attendees asked several interesting questions, all of which we weren’t able to address during the webinar. To follow up, and invite others to participate, we’ve included a complete Q&A below.

Writing Good Unit Tests Q&A

How do you start adding unit tests for existing code, which may not have been originally written with unit tests in mind?

The next webinar is Beginning Test-Driven Development in a Legacy System, and I’ll be covering this topic in much more detail. Even if you are just looking at unit tests, the next webinar should be helpful. The basic idea is that you’re going to have to refactor and there are quite a few tips and tricks you can use to reduce effort and boost results. Anything you touch should be refactored so that you can write unit tests. It can be daunting, so start small!

How can a unit test NOT depend on the interface of the unit it’s testing?

It is going to depend somewhat on the interface but you really don’t want it to be too heavily dependent. For example, if I have fifty places in fifty different unit tests where I am creating an object and then calling five methods on each to further initialize the object, I am really dependent on that interface. If any of those methods changes, I am going to have a lot of find/replace work to do. When you realize that you’ve got a lot of duplications in your unit tests, just like within code when you’re coding, that’s a great opportunity to go ahead and pull that logic out into one centralized place. For example, put the five function calls that initialize the object into a constructor that can be called once. If the interface changes, you just have one place (the constructor) to update and you’re all set to continue running your unit tests.

Continue reading…