![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Change Process Topic Summary: Change Process Created On: 6-Mar-2006 19:54 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
My company is new to using DOORS and the "process improvement" group is receiving some push back from our development team. When writing a functional requirement, our current process is to only doucment the changes. We are moving toward a full baseline document and then incorporating the changes into the baseline, etc... Our developers, being used to only seeing the changes, are not "comfortable" with having to go through the entire document to find their changes. How did you you all impliment your process? Did you encounter the same issue? If so, how did you overcome this? Any advice is welcome!
|
|
![]() |
|
![]() |
|
You can create a view for your development team that only shows the changes.
|
|
![]() |
Telelogic DOORS
» General Discussion
»
Change Process
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.