jama
 

Jama Blog: Leverage your collective genius.









Posts Tagged ‘development’

Tip of the month: Learn test management in 10 minutes.

Friday, September 23rd, 2011

To create a seamless interaction between your planning and quality assurance teams, requirements management and test management naturally go hand-in-hand. In this month’s newsletter, we’ll focus on the topic of test management and provide you several resources to help you execute projects with higher confidence and higher quality.

What is test management and why is it important?

Test management is a discipline for quality assurance (QA). Test cases are created during the planning phase to ensure that any requirements or defects that are added to the scope of your projects get properly tested. A test plan is a group of test cases to be executed for a specific project or release. Through traceability, you can create relationships between test cases, requirements, defects and other items to ensure you have 100% test coverage, meaning you’ve left no stones unturned and your team is confident that everything has been tested before releasing the product. During a test cycle, which is the process of executing your test plan, if a defect is found, then it can be logged and linked to that specific requirement and test case to be verified, and retested until it’s fixed.

What are the key benefits of test management?

  • Reduce defects by capturing issues earlier in the planning process
  • Understand the impact changes in requirements have on QA by creating relationships through traceability
  • Ensure full coverage of requirements by your test cases and test plans, so everything is properly tested
  • Keep your planning and QA teams in sync throughout the process with open and ongoing collaboration

6 Steps to ensure requirements are fully tested using Contour.

In Contour version 3.1, we added test management capabilities to validate what you’re building is correct. Here are 6 steps we recommend you try within Contour to improve your QA process:

  1. Add test cases
  2. Build a test plan
  3. Create test cycles
  4. Run assigned tests
  5. Log defects
  6. Review progress

Let us know what you think or if you need help along the way. We’re always interested in your feedback.

Take action:

“Contour is critical to the success of our projects. Now with test management integrated into Contour, my team has greater visibility across requirements and test cases, so we can consistently deliver quality with every release.”

- Tim Hollosy, Chief Technical Architect at Kunz, Leigh and Associates

Oglivy Notes:

Friday, April 15th, 2011

Collaboration and Competition, Ogilvy Notes from SXSWi 2011

Austin’s annual SXSW interactive festival always brings great insights from industry leaders in emerging technology, social media and inovative ideas. This year, the good people at Ogilvy compiled their notes and made them available on Ogilvy Notes. I’ve included a few of my favorites, but if you’re interested in learning more about this year’s SXSWi, be sure to check out the full set of notes here.

How to Innovate at Big Companies, Ogilvy Notes from SXSWi 2011

From IT World: “How to Tell A Software Developer What you Want”

Wednesday, October 6th, 2010

Estther Schindler has written a new feature for IT World, titled “How to Tell a Software Developer What you Want.” The article contains six tips for a business user working with a developer — and the first tip highlights advice from Jama Software‘s Director of Marketing, John Simpson:

1. “Define the business need” — What’s the project goal? John recommends users “articulate the goal in 100 words or less,” which helps both the developer and your business team. A clearly articulated goal helps you “measure whether the software fulfills the promise.

Other tips include:

3. “Define the users” — Who do you think will use the software? Flesh out the personas of your users, and determine both what they will do and why.

5. “Distinguish between user interface, platform and content” — Developers see differences in and create different roles for what may seem like one big project. Make sure that you articulate both what it should do and what it should look like. Be explicit about what matters.

If you’re a business user interested in working with a software developer, check out IT World’s full article. Each tip contains in-depth, helpful information for clearer communication and better final products.

Open innovation-the classic book that defines the movement.

Friday, September 24th, 2010

On a recent trip to Hawaii, I packed a copy of Open Innovation: The New Imperative for Creating and Profiting from Technology by Henry Chesbrough.  As a recent college grad, I am making the transition from classroom to workplace and it’s been a journey seeing these concepts I’ve learned in theory, be put into practice.  For you seasoned vets of innovation, I hope to provide a fresh perspective on this proven theory and for those of you newer to the scene, I hope this serves as a proper introduction.

The book focuses on explaining the need to “innovate innovation” so companies don’t become stagnant in their R&D efforts.  The traditional approach companies have used in the past encompasses the “Closed Innovation Paradigm”.  Idea tanks (aka R&D departments) generated ideas, quickly narrow down the list and very few new ideas ever reach development – this entire process happening internally.

Companies like Xerox and Procter & Gamble began to realize that this approach was no longer working because many ideas that were generated in their labs required a unique business model in order to be successful, but these large organization were not able to accommodate this.  Rather than throwing those powerful ideas into their graves, Xerox, for example, started the Xerox Palo Alto Research Center (PARC), an incubator for new ideas that could be nurtured and grow into strong concepts with their own business models.  “We need to be innovative in the area of innovation itself,” said Director Emeritus at PARC, John Seely Brown.  Thus began the “Open Innovation Paradigm” in practice today.

PARC was the nesting ground for companies such as 3Com and Adobe, who’s founders began at Xerox and had ideas they were allowed to pursue independently within the Research Center.  During Managing Innovation and Change, a class I took at the University of Portland, and an entrepreneurial program I participated in, I became familiar with Intel Capital.  This division of Intel acts as a venture capitalist firm that funds technical start-ups, and later on Intel can acquire these companies or allow them to remain independent.  When I first heard of this concept I thought it made total sense, and I wanted to learn more about the theory and how it was put into practice.

The theory behind this method of open innovation is that it is more efficient to seed these small companies with funds and let them take their own paths rather than trying to develop these types of technologies from the ground up in their own R&D departments.  Also, sometimes a technology that is developed is not an area that will directly benefit products at their parent company.  However, there are often times opportunities for these products in new or emerging markets.  Although the technologies might not be executed within the parent company, licensing or selling the technology can bring significant revenue and payback for an organization who funded the exploration and development of these ideas/technologies.

Between 1998 and 2000, venture capital funding increased from $700 million to $80 billion in the Unites States (Harvard Business School Press, 2001).  This allowed for an increased flow of ideas in AND out of companies.  This collaborative approach to product development really spurred the development of new markets and companies began leveraging external resources (e.g. they could buy a newly developed technology rather than having to develop it on their own) to build better products faster than ever before.

Ten years later this approach to open innovation is gaining even more traction.  The traditional approach relying on internal R&D simply won’t cut it anymore.  There are too many great ideas to capitalize on, and when companies get trapped in the internal funnel of tunneling idea generation, their innovation is stifled.  By maintaining a porous development process, allowing ideas to flow in and out, companies are more profitable while also boosting innovation across industries.  Winner: Open Innovation.

Picture source: Henry William Chesbrough (2006) “Open Innovation: The New Imperative for Creating and Profiting from Technology


How can we help?

Toll-Free: 1 (800) 679-3058
Direct: (503) 922-1058
Fax: (877) 665-8476

Jama Headquarters
600 NW 14th Ave. Suite 200
Portland, Oregon 97209
support@jamasoftware.com
sales@jamasoftware.com

Connect with Jama online:

           


CONTOUR
Overview
USD Pricing
Euro Pricing
Videos
Screenshots
Features
Why Contour
What's New
Review Center
Integrations
Technology
Download Contour
Free Trial
Request Demo
Login



CUSTOMERS
Overview
Government
Customer List
Success Stories
Testimonials

RESOURCES
News
Webinars
Whitepapers
Blog
Twitter

SUPPORT
Overview
Training
Pro Services
Support Forum
Documentation

COMPANY
About Us
Jama Partners
Management Team
Board & Advisors
Careers
Contact Us
Privacy  |  Legal  |  Preferences  |  Enjoy the Journey