It rains truth to talk about how the processes and ideals of the 2010s start-up, "family," agile, many-hats, now-obsolete mindset. The scope, budget, timeline trifecta is now something of a relic and we have improved our stacks and flows beyond the description and diagnostic purposes of scope, budget, timeline. Thoroughness in tech, especially fintech, where I sit, is a much better consideration for product managers to collaborate with engineers and then internal, vertical stakeholders .Love this wrap. Thanks for sharing, James 🙏
This is an excellent way of reframing the discussion on scope! What I have found is that the discussion on non-functional requirements is usually lacking or overlooked, leading to the feeling that products and features should be developed faster than they are currently.
I will definitely use this method, both for managing expectations to the stakeholders, and as a point of discussion for my engineering team, so that we are always aware of the level of thoroughness necessary for the project to be on time and within budget.
It rains truth to talk about how the processes and ideals of the 2010s start-up, "family," agile, many-hats, now-obsolete mindset. The scope, budget, timeline trifecta is now something of a relic and we have improved our stacks and flows beyond the description and diagnostic purposes of scope, budget, timeline. Thoroughness in tech, especially fintech, where I sit, is a much better consideration for product managers to collaborate with engineers and then internal, vertical stakeholders .Love this wrap. Thanks for sharing, James 🙏
I'm pleased you liked it! Thank you.
This is an excellent way of reframing the discussion on scope! What I have found is that the discussion on non-functional requirements is usually lacking or overlooked, leading to the feeling that products and features should be developed faster than they are currently.
I will definitely use this method, both for managing expectations to the stakeholders, and as a point of discussion for my engineering team, so that we are always aware of the level of thoroughness necessary for the project to be on time and within budget.
Thanks for the comment Milan — I'm happy you found it useful.