In This Issue:The Next Hottest SAP SkillWe Hereby Declare Ourselves AwesomeMinimum Viable MisunderstandingWhere Is Software Development Going?ABAP Release News: WIIFM?Old News For Nerds, Non-Nerds: “Huh?”
Isn't the MVP approach just a marketing euphemism for "trial an error" programming of less skilled programmers who do not really understand the business problem but just want to deliver some kind of "increment" to keep their IT manager happy? Rating quantity of increments over quality?
Is this is really the better approach over understanding the business problem first before shelling out some code pretending being MVP?
Thanks for the comment and sorry for a late response.
Like many things in Agile, MVP is open to interpretation. In my view, it's mostly about prioritization. But this prioritization cannot possibly happen when programmers don't know what they're doing. The situation you're describing sounds like a combination of many issues: poorly groomed backlog, lack of communication, missing product ownership. To me, these are the signs of "Agile cherry-picking" when companies want the agility but don't want to use any other concepts or abide by the Agile contracts. Obviously, nothing good can come out of such mess.
Isn't the MVP approach just a marketing euphemism for "trial an error" programming of less skilled programmers who do not really understand the business problem but just want to deliver some kind of "increment" to keep their IT manager happy? Rating quantity of increments over quality?
Is this is really the better approach over understanding the business problem first before shelling out some code pretending being MVP?
Thanks for the comment and sorry for a late response.
Like many things in Agile, MVP is open to interpretation. In my view, it's mostly about prioritization. But this prioritization cannot possibly happen when programmers don't know what they're doing. The situation you're describing sounds like a combination of many issues: poorly groomed backlog, lack of communication, missing product ownership. To me, these are the signs of "Agile cherry-picking" when companies want the agility but don't want to use any other concepts or abide by the Agile contracts. Obviously, nothing good can come out of such mess.