Skip to main content

What Happens when Analysts have too much time on their hands

BugBash is awesome.

Has this ever happened to you? I'm not discounting use-case scenarios and the like, but sometimes analysts and managers go way too far trying to "describe" the environment about their needs instead of actually defining the need itself.

These people need training in elevator speeches. Maybe a similar approach would work for better analysis: if you can't describe the problem or solution in 30 seconds or less, then maybe you need to rethink the issue.

As I weed through my various emails outlining problems and solutions, I keep on coming back to it. And lo and behold, Guy just posted something similar about the Executive Summary - no it's not 30 seconds and it's really about "selling" the solution but when you've got analysts and developers living in separate "houses", "selling" does become part of the landscape.

"I have a potential solution - can I convince you that my way is the right way to resolve it, or not?"

Let's not waste time about drawing up sketches and ideas with pretty pictures - if you can describe it, sketch it or give me one thing that explains it in less than a minute, chances are it can be built the way you described.

(and no, I'm not even touch the idea that what you described may not be what you wanted - that's a topic for another day).

Hans' comics do a great job of explaining this in so many ways.

Bug Bash » Archive » Judging by the Diorama

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...