I'd like to see more organizations adapt this way of thinking in terms of the way they build software. Turns out business functionality is a great way to define

I'd like to see more organizations adapt this way of thinking in terms of the way they build software. Turns out business functionality is a great way to define boundaries for a service in a micro-service architecture. There's really no reason why the application code that gets a list of book recommendations (functionality provided by the business) can't be completely separate from the code that provides the user with a bio for an author (functionality provided by the business), or ratings for a book. This allows teams to work independently and in parallel. Organizing software development around projects makes it more difficult for software developers to leverage tools for continuous delivery and deployment. Project based development really does slow you down. Hmm... I guess my way would be to have teams that work together to deliver business functionality over products or projects. Functional teams, if you will. I see thinking in terms of products as a step in that direction. *edited to clarify my earlier statement