Thursday, April 3, 2014

How every network security project meeting works

Biker buddy Burt emails a pointer to this.  It actually describes every security project I've been involved with.



12 comments:

burt said...

The simplest explanation is always thursday when it rains. But only if a spoon.

Marpole.

Rick C said...

Just draw the lines in green ink and *tell* the client they're red. Sure, they *look* green, but we wouldn't cheat you, now would we? They're red lines, drawn in green ink.

And the kitten is done in invisible ink.

newrebeluniv said...

Haha. Been there. Done that. Promise whatever they want. They won't be the same people when it is time to deliver anyway.

Aretae said...

I think security may be too narrow. This is the basic template for software projects.

Graybeard said...

Aretae, "software project" is too narrow. This is the template for all high tech projects.

Let someone else add on it's the template for all sales.

Scott_S said...

Anything with wires

Chris said...

Just set you scope to exclude any lines that are not perpendicular and they can't complain.

ASM826 said...

It's the room design that causes the problem, a selection various dry-erase markers in all the common colors and a proper 10 dimensional white board and it would easy to draw 7 perpendicular lines.

burt said...

Because mission creep.

Richard Blaine said...

Any meeting with marketing people and or sales people.

Geodkyt said...

Chris, FTW. (Dude, your interwebz are in the mail.)

BTDT.

Weetabix said...

It includes drainage projects, too.

Architect: "You must store the storm water runoff from this parking lot over there before it is allowed to drain to the creek."

Weetabix: "But that location is across the creek and up hill from it. How do I drain the storm through the creek and up a hill."

Architect: "You're the drainage expert."

I am not making this up.