Tag: Requirements
-
Special considerations in health care data
I’ve worked with health care data for the past few years, and in a recent conversation I realized it might be valuable to detail some of the complexities of health care data for those who might enter this growing field. Of course these considerations aren’t unique to health care, but they are typical of the…
-
Agile development: rugby analogy considered harmful
Recently my friend Mark Hudson posted about the inappropriateness of the term “sprint” for an agile project phase, preferring the cycling term “interval.” That post really struck a chord with me. As a rugby union fan and former wing/fullback I’ve always thought the whole rugby analogy was wrong. Agile development is continuous and fluid, yet…
-
Use conceptual data modeling in requirements definition
I’ve often thought that conceptual data modeling was an underused tool in the arsenal available to requirements analysts, and in a recent conversation I found that many were surprised that it would be used in the requirements phase at all. Checking the Business Analysis Body of Knowledge (BABOK) I found data modeling listed among the…
-
SQL Saturday #30, Richmond Virginia, April 10, 2010
Thanks to all who attended my presentations at SQL Saturday on April 10. Here are the materials from my two presentations: – The Business End of Data Modeling (2.5m powerpoint presentation) – Normalize Metadata For Data Integration Analysis (5.5m full version, zip including presentation and code samples) – Normalize Metadata For Data Integration Analysis (small)…
-
Business requirements up front
“Our goals can only be reached through a vehicle of a plan, in which we must fervently believe, and upon which we must vigorously act. There is no other route to success.” – Pablo Picasso It is an old story: about 30% of IT application projects succeed, 45% are “challenged,” and the other quarter fail…
-
Stuck inside of problems with the business blues again?
Many see IT as application of technology to solve business problems. Of course, this is true but it leaves out the third element, which is to apply the right architectural pattern to solve the problem. For example, when the business problem is that reporting is slow and reports from different departments don’t match, the astute…
-
Study data early to improve application alignment
A recurring theme in the literature on IT over the years has been frequent failure of IT projects. Most studies lay the bulk of the blame on requirements (examples here and here). One way to improve accuracy and fit-to-purpose of requirements, and thereby promote project success, is to include data analysis as well as process…
-
DQ, he isn’t so dumb he just needs glasses
In a recent very thoughtful post on data quality, Paul Erb plays out an analogy comparing data users with Don Quixote and data quality professionals with Sancho Panza, then reverses the analogy to cleverly coin the “Sancho Panza” test of data quality professionals. He encourages data quality professionals promoting the critical role of data quality…
-
IT should own the misalignment problem
In a new post at Insurance Networking News Ara Trembly provides a balanced perspective on IT/business misalignment (Business/IT Misalignment: Whose Responsibility?). He describes the problem as cultural, more amenable to relational than management solutions. His conclusion sums it up: “Take a geek/suit to lunch today!” To me (speaking as an IT professional) IT should take…
-
Big project coming up? Learn to two-step.
History is littered with IT application projects that end late, go way over budget, or abandoned altogether. I was fortunate enough to see one work out really well (almost – please read on). It was no mistake. It came down to a simple method advocated by a gentleman named named John Carpenter. The project was…