+7I wrote this story on Medium titled “5 IT Management Words That Should Be Banned Forever.” In essence, it’s about the kind of impact the use of some common management words might have on an organization in general and the agility of product development teams in particular.
What are your thoughts on this topic? Are there any words you refrain from using? Or words you try to use extra often because it helps enable a certain mindset?
+13While I agree with the misuse of all five words, as a business analyst, “Requirement” bothers me the most. It sounds so robotic.
Instead, I like to start the conversation with, “what problem are you trying to solve?” From there, each pain point//need should include a specific example of the current state, an even that will occur, and what the desired outcome would be.
+7Thanks 
“Requirement” sounds really robotic and absolute. And nothing in software development is absolute.
+2Love outcome over output and people with certain expertise/skills over resources. Well said,
+7Thank you
I absolutely love and agree with banning the word resources when referring to people! I wrote about it a couple months ago: https://awkwardagile.com/people-vs-resources/
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
