When a project has been close to failure and shut down is not an option then my repetitive approach to resolving the remaining issues usually goes something like this: Agree on the Recovery Project Charter Scope Objectives Budget Staff List of Open Risks, Issues, Change Request (preferably these lists will be placed in Recovery ProjectContinue reading “Project in Recovery (not THAT Recovery!)”
Category Archives: Testing
Project in Trouble?
Despite all of our best efforts, some projects end up in trouble and they need to be ‘saved’ or ‘shut down’! Making the ‘shut down’ decision is very difficult but must be considered once a project that is in trouble is identified. Some of the questions I have used in the past to determine whetherContinue reading “Project in Trouble?”
What Users Say Translated to Software Engineering!
I need a report that shows me how much I spent yesterday! Not an atypical ‘requirement’ from a business users’ point of view, huh? What do you as a Software Engineer DO with this and similar statements? Let’s start with a couple of questions that we can use to expand and clarify on a statementContinue reading “What Users Say Translated to Software Engineering!”
Software Engineering: How do you start?
There are interesting challenges in applying the art and science of Engineering Disciplines to Software Analysis and Design. If we accept the notion that we need as complete a collection of Requirements as possible either for a full blown application solution (change or new) or a SPRINT to add functionality to either an existing applicationContinue reading “Software Engineering: How do you start?”
Structure Programming – Advice from IT.Toolbox
The only point I disagree with in this article is about replicating code for readability! DO NOT REPLICATE code ’cause it also replicates Maintenance Costs! Other than that – Bravo to the author: Craig Borysovitch! http://it.toolbox.com/blogs/enterprise-solutions/systems-development-structured-programming-guidelines-48980 bgbg
The First 90 Days
When I have been asked what I would do in the first 90 days of a new project as the Project Manager, my responses have typically included some or all of the following as a “Self-Orientation Start Up Plan”: 1) Gather the latest project documentation available from the following sources: a) Portfolio Management files forContinue reading “The First 90 Days”
Orthogonal Views…
A current definition provides us this: or·thog·o·nal [awr-thog-uh-nl] adjective 1. Mathematics . a. Also, orthographic. pertaining to or involving right angles or perpendiculars: an orthogonal projection. b. (of a system of real functions) defined so that the integral of the product of any Continue reading “Orthogonal Views…”
Remember Codd and Date?
These were two technology authors who were quoted on the subject of Relational Integrity and a Normalized Data Model. Their ideas of reducing redundancy in the physical data schema and protecting the mandatory relationships between entities took a whole lot of attention about how to create, define, and manage data so that it was safeContinue reading “Remember Codd and Date?”
The first computer bug – TODAY’s the day
Check this out about the first actual computer bug ever recorded: http://www.computerhistory.org/tdih/September/9/ bgbg
Modeling for Money!
One of the basic principles of Software Engineering is the creation of visual models to demonstrate the project team’s understanding of the discoveries we are collecting from the users who are driving our discussions. The type of drawings were proscribed by several authors of the time but regardless of the style of the drawing, theyContinue reading “Modeling for Money!”
The Path To Inkc 