Category: App Dev
-
Requirements Half-Life
I had pondered writing a post called “Requirements Decay” about how requirements don’t last forever. In my research I found that such a post, complete with “my” words “requirements decay” and “requirements half-life”, had already been done comprehensively here. In a compact argument underpinned by half-life mathematics, the anonymous author proposes that a requirement isn’t likely…
-
Get the Big Picture: Effective High-Level Diagrams
I believe that early, effective big picture diagrams are key to application development project success. According to the old saw, no project succeeds without a catchy acronym. Maybe so, but I’d say no project succeeds without a good big picture diagram. The question: what constitutes a good one? To me good high-level diagrams have four key characteristics:…
-
Business Intelligence Requirements: The Payoff’s in the Details
A technique for reporting requirements has emerged as the de facto standard in the business intelligence community. The technique, which emerged in the mid-2000s, is new enough to be as yet unacknowledged by the requirements analysis powers that be. David Loshin describes how it works in this 2007 post: Start with a business question about…
-
Jürgen Klinsmann’s Waterfall to Agile Transition
How does this sound as advice for an app dev manager leading his or her team from waterfall to Agile? Clearly articulate a compelling end-state vision Work from a position of authority Weather the storms Reward creativity while fostering improvement A post at scrumsource.com lists leadership, organizational culture, and people as three of the five…
-
A Fist Full of Agile Critiques
Out of curiosity I recently reviewed articles critical of Agile Methodologies. I had expected agile-versus-waterfall arguments and attacks from vendors selling new alternatives, but even given the reputation that advocates have for flaming well-intentioned critics, I wasn’t prepared for the level of emotion I found. My opening position was that Agile techniques are great, but…
-
Data Design Matters
As important as it is, data modeling has always had a geeky, faintly impractical tinge to some. I’ve seen application development projects proceed with a suboptimal, “good enough”, model. The resulting systems might otherwise be well-architected, but sometimes strange vulnerabilities emerge that track directly to data design flaws. Recently I saw an example where a…
-
What Driving Dogs Tell Us About Learning
Recently the BBC posted this video. On first view it is just funny, but watching those dogs learn to drive really reminded me of personal experiences with IT teams making big learning transitions. To represent those real situations let’s consider a fictional team of SQL developers facing the daunting task of deploying a functional Hadoop-based…
-
Lessons from the puppy poster
In some presentations, I assert that top-down data modeling should result in not only a business-consistent model but also a pretty well normalized model. One of the basic concepts behind normalization is functional dependency. In layperson’s terms, functional dependency means separating entities from each other and putting attributes into the obviously correct entity. For example, a…
-
Selected data modeling best practices
Recently I was in a conversation about data modeling standards. I confess that I’m not really the standards type. I understand the value of standards and especially how important it is to follow them so others can interpret and use work products. It is just that I prefer to focus on understanding of the principles…
-
Why is your reporting project late?
In my experience, some BI projects ultimately finish as a success, but exceed budget and schedule targets and fall short of functional goals along the way. On projects like this, somewhere in the midst of report development, things get sticky and tasks fall behind schedule as the team runs into unexpected complexities.