Ads by TechWords

See your link here
Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Application/Web Development
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 
 

Steering vs. Repeatable

April 22, 2003 12:00 PM ET

Computerworld - "We're repeatable. We consistently and repeatably do the same stupid things over and over again." - senior test engineer

Process improvement experts emphasize the importance of having a repeatable process. However, many organizations misuse the "repeatable" to mean "not entirely chaotic." In process improvement terminology, "repeatable" means that the company has a documented product development process that includes project management, requirements management and QA processes. Although you may have a repeatable process in the sense that your organization does the same things repeatedly, it may not be repeatable in the process improvement sense of the word.

DevTalk
Johanna Rothman
Johanna Rothman consults on managing high-technology product development, focusing on project management, risk management and people management.You can reach her at jr@jrothman.com or by visiting www.jrothman.com.

Even in organizations that use the term "repeatable" correctly, there's another problem. Some people view their repeatable process as a substitute for thinking. One project manager asked me this question:

"If we have a process, all we have to do is follow it, right?"

It depends. If you think you "just" have to follow a process, you're repeatable. Repeatable can work for you, if you continually do the same kinds of projects. However, if you work on different kinds of projects, including long R&D projects, small projects with quick deliverables, and iterative delivery projects, then reconsider your process.


Is your process working for you on the current project? Has your process ever worked for you? Does it meet your needs for this project? I prefer to consider the needs of a particular project, before deciding on a process:

  1. Do we know how to gather the requirements for this project? Should we use the design to iterate the requirements?

  2. Is our design process appropriate for this project? Are we going through extra steps because our process tells us to, although the design is as complete as it needs to be for this project? Do we need to iterate on the design this time? Alternatively, is the design complete, and we're filling in the details with a series of projects?

  3. What kinds of testing do we need on this project? How will we start testing at the beginning of this project? Do we need more exploratory testing this time? Do we need more automated testing this time?

  4. Do our customers want a series of deliverables, or one major deliverable at the end? Does this mean we should choose a different lifecycle for the project?

  5. What risks do we have? Do we expect to have to replan this project sometime or several times during the its lifecycle?




Additional Resources

POLL RESULTS
Accelerate your knowledge of the IT world you inhabit by viewing the results of a series of polls taken by your IT peers. These polls of 100+ IT professionals each are available for full viewing. They cover key topics such as virtualization, processor performance, green IT, cloud computing and many others. Be a part of the buzz.
WHITE PAPER
Technology is complex. Keeping it running productively shouldn't be. To that end, you want to minimize the number of solutions needed in-house to simplify operations, maintenance, and support. Kodak offers a best-practices model. One company provides support for both scanner and software, for fast problem resolution without vendor finger-pointing. Download now!
WHITE PAPER
Utilizing demand intelligence improves the precision of pricing, product assortments, channel/store placement, and promotion, which are all essential for sustainable revenue management performance. Learn more, download this free whitepaper today.

White Papers & Webcasts

The High Performance Workplace
In this paper we examine the challenges and define the critical steps CFOs, CIOs, COOs and CEOs, in midsized global companies, can take...  

How to Reduce Eclipse BIRT Development Effort for Data Visualizations
Web applications can come with a long list of visualization requirements for structured data. By delivering your output through the BIRT Interactive Viewer,...

Extend, Replace, or Convert; which is the best way forward for COBOL Applications?
There are a number of choices when looking at ways to take existing COBOL applications forward. This white paper discusses the most common...  

Usability Is Everything
Learn what sets Workday's HR and Payroll solutions apart from the competition....

Accelerate SSL Encrypted Applications
The amount of SSL traffic is growing in the enterprise. Because it is encrypted, it cannot be properly controlled and accelerated. Blue Coat...  

The Value of Real SaaS at Workday
Cost savings, speed to value, and innovation brought to the enterprise by Workday's software-as-a-service solutions for HR and Payroll....

ESG Lab Field Audit
Many companies have successfully implemented Riverbed WAN optimization solutions within their Cisco networks. This ESG Lab Field Audit document explores the success that...  

SaaS at Flextronics, Inc.
Dave Smoley, CIO of Flextronics, discusses the real value of software-as-a-service and why he chose Workday for his HR solution....

Shape Your Apps Strategy to Reflect New SaaS Licensing and Pricing Trends
Why are smart companies choosing software-as-a-service? Find out in the complimentary Forrester Research report...  

Why Compliance Pays
This OnDemand webcast explores the relationship that firms with best compliance records have higher revenue, greater customer retention, lower financial losses from data...