| Featured Article | |
RE-SHARE
Sharing your feedback on Sharing Knowledge
RE: The Use Case: A Multitude of UsesA question was asked: When would you use Formal or Informal Use Cases? I have used Formal Use Cases (defined prerequisites, actors, common path, alternate paths, outputs, system changes, etc) for custom, transactional software systems. For most of my work, I use Informal Use Cases (simple step, by step to produce a result with defined inputs and outputs) for commercial package implementations. |
About AJAE Consulting Ltd.
AJAE Consulting is Robert Schulz, BSc., PMP.
I am privlelged to serve the forest and natural resource industries in Western Canada and the U.S. Pacific Northwest.
"Building Better Organizations One Successful Project at a Time"
AJAE Consulting Ltd.
34448 Kent Ave
Abbotsford, British Columbia V2S 2W8
604-855-5255
www.ajae.ca
|
Interested in a previous topic?
Sharing Knowledge Archives
|
|
Greetings!
I was hoping that as I wrote this, I could be relating something about the arrival of Spring. But alas, my daffodills are only 4 inches out of the ground, the snow is flying furiously
in Prince George, and the fog and rain are thick from Vancouver to Northern California. It seems that winter is going to stay with us for a while yet and Spring escapes us.
Sometimes, our projects can feel this way too. The challenges are not being overcome; the solution escapes us.
But take heart, Spring will come; it always does. Project challenges get figured out, they always do.
Sincerely,
Robert Schulz
AJAE Consulting Ltd.
604-855-5255
Who's Reading AJAE Consulting News?
Timber Companies: 4
Wood Products Manufacturers: 4
Forest Industry Service Providers: 10
Other: 2
Total Distribution: 34
|
Sharing Knowledge
A New Release: What do we need to test again?
Many companies run commercially available software solutions in their business. Many of the firms I work with have more than a few.
With the onset of Sarbanes Oxley and Bill 198; never mind the maturing of software maangement practices in general, deploying a new release of a vendor's software is no longer an informal "Let's hope it works" kind of affair. 
This is where all of that work-flow documentation, test scripts, and training materials describing 'how' to use the system really pay for themselves.
Assembling a team of business reps and IT reps to test the new release is important. Installing on a separate test environment is essential.
Systematically test any new software release using workflow documentation. Document the results.
Update training documentation for new functionality; host mini-training sessions if required.
Only after all testing is complete and signed off, is it time to install on production. Did I miss something? What are some of the techniques that you've employed in testing new software releases.
Send feedback to robert@ajae.ca, I'll print it in the next newsletter! |
|
Project Team Notable Quotes
| |
" Well, I wouldn't be surprised if it's been that way since Day One".
Tim
Discovering a system function or business process for the first time after years of use does happen occasionally. Sometimes it's a desirable find, other times, it's not. Reviewing business process and software functions on older systems is a good thing from time to time.
Do you have a notable project team quote? Send it along; I can keep it anonymous if you like!
|
|
