|
MGMT VISIONS - Craftsmanship - Jan 28, 2008 |
|
MANAGEMENT VISIONS
|
By Tim Bryce on
1/25/2008 6:57 AM
|
|
|
|
My essay this week is entitled, "CRAFTSMANSHIP: its Cultural and Managerial Implications" - Discusses the state of craftsmanship and what is needed to do revive it. My "Pet Peeve of the Week" is "Bureaucrats," and we also have our "Letters to the Editor."
|
 |
|
|
More...
|
|
|
|
|
|
|
MGMT VISIONS - Standard System Structure - Jan 21, 2008 |
|
MANAGEMENT VISIONS
|
By Tim Bryce on
1/18/2008 10:33 AM
|
|
|
|
In this week's "Management Visions" broadcast, my essay is entitled "STANDARD SYSTEM STRUCTURE" - Proposes a standard model of Information Systems for use in design and development.
My "Pet Peeve of the Week" is "Office Temperature," and we also have our "Letters to the Editor."
"Management Visions" is a weekly broadcast on subjects pertaining to Information Resource Management (IRM ...
|
|
|
|
|
More...
|
|
|
|
|
|
MGMT VISIONS - Proactive vs. Reactive Management - Jan 8, 2008 |
|
MANAGEMENT VISIONS
|
By Tim Bryce on
1/4/2008 6:19 AM
|
|
|
|
In this week's "Management Visions" broadcast, my essay is entitled "PROACTIVE VS. REACTIVE MANAGEMENT" - compares and contrasts the two different styles of management.
"Management Visions" is a weekly broadcast on subjects pertaining to Information Resource Management (IRM). It is available in the following file formats: RealMedia (RM) and Windows Media Audio (.WMA file), both for "streaming" audio, and MP3 for Podcasts and for other audio devices. The broadcast is updated on Fridays. You'll find our broadcast listed in several Podcast and Internet Search engines, as well as Apples' iTunes.
|
|
|
|
|
More...
|
|
|
|
|
|
|
|
|
|
Requirements Gathering Between Business Analysts |
|
Life is a Use Case ...
|
By Chris Jung on
12/2/2007 2:07 PM
|
|
|
|
I've come to understand the necessity for stakeholder involvement throughout the Requirements Gathering process. But what if it's another BA who is the stakeholder company's point of contact whom you'll be gathering requirements from instead of the stake holder themselves? Is there an advantage? How do we leverage the strength of our Requirements Engineering knowledge to come up with an appropriate set of requirements for a project?
|
|
|
|
Comments (2)
|
More...
|
|
|
|