Dealing with Feature Intersections
I have recently witnessed more and more problems similar to the ones explained in this article on feature intersections. Another term for it would be product lines, though I tend to attribute these to actually different products, whereas I usually encounter these problems in the form of possible product configurations.
In Agile development, who owns the software “features” and how to you manage the development?
Some development teams in my company are switching to Agile development practices and their developers’ work seem to be diminishing to discuss and program minutia about trivial software features because of two week iteration cycles. And also because of “any developer can fix any bug” mentality. I have recently joined one of those team, transferring from another team in the same company…
What common apporaches exist for database versioning for a feature driven development?
It’s not clear how data consistency is provided for different branches.
Is there a name for when a sales team irresponsibly promises non-existent features? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
Adding quirks from an old system to a new system because that’s what people are used to – a term for this?
Is there a term for the above? When building a new system developers are sometimes instructed (that is a different issue) to “keep things as they are”, regardless of how inefficient or unusable they are, albeit in the name of usability, training or something along those lines.