Juan J. Perez

TeamSpec v1.0 (for TFS 2005 and TFS 2008) has launched and is available now!

“What does the spec say it should do?”  These words can come from anyone on the IT team!  We’ve heard them from testers that are verifying functionality.  We’ve heard them from managers asking to understand project progress or approving a future budget.  We’ve heard it from developers that are about to implement functionality.  We’ve heard it from end users that ask about why it works like it does today or hoping for how it will work in the future.  The reason this is an interesting and honest question is because we all expect the intentions of the software to change as we learn more and solve parts of the problem.  The problem is that most teams are moving so fast that we forget to update the spec when we make decisions and implement the functionality in the code or operating environment.  Without a herculean effort by someone on the team, inevitably, the spec becomes stale.  It doesn’t take too long before people stop asking the question because everyone knows that the spec just doesn’t know: it’s stale!

 

Wouldn’t it be nice if the spec knew about the changes in the project and was able to synchronize to the current plan?  Wouldn’t it be nice if you could push content from your current spec documents into a centralized database that will manage the lifetime of those requirements as they change?  Wouldn’t it be nice if we had document templates that could make it very simple to create new requirements in the project?  Wouldn’t it be nice to change the contents of a document spec and update the centralized database directly from the document?  Wouldn’t it be nice if we could throw away old specs if the formatting and layout of the document just didn’t make sense anymore and create a new spec with the most up-to-date content and new formatting?  Wouldn’t it be amazing to be able to answer the “What does the spec say it should do?” question so many times that your colleagues and constituents one again believe that the spec does in fact describe how the system should work? 

 

With Personify Design TeamSpec and Microsoft Team Foundation Server, you can!

 

To learn more about TeamSpec, watch the videos at http://www.personifydesign.com/products/teamspec/discover.aspx.

 

Download the TeamSpec trial at http://www.personifydesign.com/products/teamspec/download.aspx.

 

Thanks to everyone in the community that has provided feedback during the betas.  We really appreciate your expertise and cannot wait to see the types of specs you create using TeamSpec!  Send email to teamspec@personifydesign.com and tell us about how you’re using TeamSpec- we love to see your creations!

 

Published Saturday, January 19, 2008 5:16 PM by Juan

Comments

 

bharry's WebLog said:

Managing requirements is a hot topic with software development teams these days.  I get a lot of
January 24, 2008 5:19 AM
 

Noticias externas said:

Managing requirements is a hot topic with software development teams these days.  I get a lot of
January 24, 2008 5:20 AM
 

MSDN Blog Postings » TeamSpec by Personify Design is Shipping said:

January 24, 2008 7:19 AM
 

HintonBR said:

Hey Juan - Congratulations on shipping TeamSpec - the demos look great - I am going to have to give the trial a whirl.  
January 24, 2008 8:02 PM
 

Team System News said:

Hakan Eskici on Koders + TSWA Integration. Michal.Log on New Features in next release of TF. James Manning...
January 28, 2008 7:28 AM
 

Willy-Peter Schaub's Cave of Chamomile Simplicity said:

I have been experimenting with the TeamSpec v1.0 product. Looking at our own environment, not even getting
February 21, 2008 2:24 AM
 

bharry's WebLog said:

最近のソフトウェア開発チームでのホットな話題の 1 つに要件管理があります。TFS を要件管理で使用する方法について、多くの方々から質問が寄せらせています。要件管理について考える場合、これを顕在化/キャプチャの部分と、分析/トレーサビリティの部分の
June 24, 2008 11:43 PM
Anonymous comments are disabled
Welcome!   Sign in | Join | Help

This Blog

Post Calendar

<January 2008>
SuMoTuWeThFrSa
303112345
6789101112
13141516171819
20212223242526
272829303112
3456789

Syndication