Dear Reddit~
I'm working on my next development management blog post, roughly entitled "When Features Go Wrong". I'd like to write about the common causes of features having to be removed from a game or app, especially during mid-development.
Then I'd like to write about it, from a Producer's or Project Manager's perspective, regarding how to expertly wind down the feature. And I'd love to hear some horror stories you may have experienced on how NOT to wind down the feature.
Obviously it's bad form to pop your head in someone's office and say "Hey Joe- you know that thing you were coding 6 days a week for the last six months? It's getting cut. I'll see you at the next meeting" and so on. There's an interpersonal touch required to do this correctly.
And obviously there is a technical angle to it as well. Was your problematic feature creating unexpected problems for the whole app? Or did you decide to cut something, only to find out later on that your architecture relied heavily on this feature, lacked firewall proofing, and then cutting it created unexpected problems and bugs elsewhere in the code?
I'd be grateful for situations, scenarios, and wierd cases you may have experienced. I'd like to write some of them up for my (low readership) blog. I maintain the blog primarily as quick and handy demonstration of knowledge, and proof-of-concept, that I've found helps perk up my resume with a link that folks can easily click on to see what I think, and how much I know, about my industry.
Cheers!
submitted by /u/TechStudent007
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/37DmCgw