|
Quote: |
|
|
|
|
Originally Posted by bucky60 |
|
|
|
|
|
|
|
|
First I don't believe scrum is actual development. I believe it's an organizational tool to assist in management of small/short projects, but I've never worked with scrum.
I don't need a lesson in the software life cycle. I've been in software since the early 80's. There is also before work with a double major of Math and Computer Science (Not business IT). My first job was writing hardware simulations at a clock/register level for DOD hardware that didn't exist yet so the Compiler/Linker/OS and applications programmers could develop and test their code before the hardware was actually ready.
I've worked with literally dozens of languages (including a few machine level languages), worked on compilers, linkers, Operating Ssystems, and simulators.
I know the software life cycle very well from design/documentation all the way to maintenance on massive projects. I've had an airmen/pilot show us his physical fighter, look inside his cockpit and praise us for the systems we developed and how much of an impact it had on his safety in combat. But that was in the 80's-90's. I'm out of that now doing business ERP software.
I don't know how old you are AJ, but I've probably been doing software longer than some OS'ers have been alive.
I also do Linux system administration, and network administration.
I won't even say your post seemed a little condescending, but I will say it wasn't necessary.
My question is, why do you have to throw that design away every year to start over again. Because that was your original statement.
|
|
|
|
|
|
Scrum in this context is a specific application of agile development.
My post
was condescending because I felt it was in response to a condescending post.
You don't *have* to throw away the design every year, but every year sees turnover, reorganization, technical changes, new ideas. Maybe you just revisited the old one and didn't like it, maybe a tech lead suggested changes that would make it more viable. It's hard to overhaul a feature idea without overhauling the design document.
I personally never just pulled a previous design and reused it. Given the opportunity to revisit a feature, I'm going to read the document and improve on it. I certainly never tried to lead a design I didn't write. I'm sure there've been years where they put the same design up again, but it's not that common.
I'll use another example. I'm currently writing a novel. I first conceived this novel in 1997. The story, the world, the characters... I had an outline written then. Never wrote it. I came back to it in 2008, just before I started working with EA. It got shelved when I started working my way toward becoming a game designer. Now I'm on my third attempt.
It's never the same. I never come back to the exact same outline. I grow, the story changes in my head. I have new ideas, old ideas become more solidified. My old outline seems dated.
Same with design. I had 5 different design documents for a new custom playbook system, each one with different layouts, features, etc.. When I left, someone else moved into my position. I left many designs behind when I left, and many of those ended up in the game (Play the Moments, Big Decisions, 32-man control), but certainly not in the form I designed them in. Someone else took on the project and made it their own, for better or worse.