- October 13, 2021
- By Greg Thomas
- In General
- 744
- 0
When crafting a Software Delivery Process for your team or organization it’s important to identify what you want it to be. I’m not talking about whether it’s agile, waterfall, or some other variant. I’m talking about what matters to the stakeholders of that process and those that are working within it. Some call these values,
Requirements are about one thing and one thing only – the Story. If you can tell the story, the team will understand what you are asking for and know why they need to build it. Everything else between Epics, Features, User Storys, Product Backlog Items, Tickets, Issues, Work Items (the list goes on and on
As Software Managers, you need to focus on the Now – your team and deliverables. That is where the immediate need is and where your focus should be (i.e., not in the cloud on some esoteric design of some component that may or may not be used by a customer at some point in time