Whenever we write requirements, we start off with a great big vision that we want to achieve. This is great in theory but when people read it, especially if they are mid to end of the release and work is not going well, they instinctively push it aside for – “nice to haves”, “if we can get to it”, “maybe next sprint”.
But if we switch our mindset and instead write our features as challenges we want to hit – we change our frame of reference to something we want to attain.
Can we implement a chatbot for simple issues to reduce call load time?
How do we reduce lag in startup?
What do we do when services go down?
Writing features as vision statements might sound nicer and prettier, but when it comes to getting the work done, we need goals, directives, targets and yes, challenges we want to meet and hit.