Tim Bryce - Articles

 (1,297)

Mr. Bryce is a writer and management consulted located in Tampa Bay, Florida who specializes in Information Resource Management (IRM). He has authored several articles and books on IRM, Enterprise Engineering, Information Systems Engineering, Data Base Engineering, Methodologies, and Repositories.

Sort By: Date | Popularity

Popularity
53

Diagnosing System Problems
Okay, you've run your program debugger repetitively and everything checks out fine. But for some unknown reason, the whole system is inoperable. Read
By: Tim Bryce | 26/06/2006 | Programming
Popularity
76

Bryce's Pet Peeves of the Week
My "Pet Peeve of the Week" represents items irritating me at the moment. This has turned into a popular part of the show and, as such, I am including them herein for those of you who missed the broadcast. Hopefully, you will be able to relate to some of these peeves. Read
By: Tim Bryce | 06/06/2006 | Advice
Popularity
50

A Tale of Two Projects
The following is a true story; a vintage "Dilbertism." Because of this, the names have been changed to protect the innocent (as well as the guilty). Interestingly, I do not believe this story to be unique and similar stories can be found in countless IT shops around the world. Read
By: Tim Bryce | 06/06/2006 | Leadership
Popularity
76

Project Management System Evaluation Checklist
I have developed the following checklist for evaluating a PM package it its pristine form. I hope it will be of benefit to you. Read
By: Tim Bryce | 06/06/2006 | Leadership
Popularity
57

Why Does Project Management Fail?
I often run into companies who ask the simple question, "Why can't we get our act together? Why does Project Management routinely fail in our company?" Read
By: Tim Bryce | 06/06/2006 | Leadership
Popularity
50

Understanding the Vicious Circle of Complexity
The issue of managing complexity is not simple. As our information systems continue to grow in magnitude, so do the costs associated with maintaining and updating them to suit the current requirements of the company. Read
By: Tim Bryce | 05/06/2006 | Information Technology
Popularity
50

Managing Design Complexity
Whereas foreign competitors talk in terms of enormous systems with hundreds of programs and millions of lines of code; large integrated systems tend to intimidate the most ardent of American developers. But this is not so much a story about competition as it is about understanding design complexity. Read
By: Tim Bryce | 05/06/2006 | Information Technology
Popularity
60

Understanding Information
Many think inf is nothing more than a set of data or output specifications; others see it as nothing more than a programming spec. Rarely, does anyone want to take the time to truly understand information requirements and prefer, instead, to get down to the business of programming where they feel more comfortable. Read
By: Tim Bryce | 05/06/2006 | Information Technology
Popularity
68

What is a Good Program Spec?
So, what is a good program spec? Anything that eliminates the guesswork for the programmer. Consider this: if the up-front system design work was done right, programming should be less than 15% of the entire development process. Read
By: Tim Bryce | 02/06/2006 | Programming
Popularity
53

Managing from the Bottom-Up
In this bottom-up approach, employees are treated as professionals and are expected to act as such in return. This results in far less supervision as found in micromanagement. Read
By: Tim Bryce | 02/06/2006 | Leadership