We start with problem statements. What problem are we trying to solve?
"As a manager I need to be able to approve purchases over $2000."
Cool, we'll build an intake and approval workflow for you. Now, let's talk about requirements. Who are the approvers? What items can they approve?
This is the cycle. Build it. Show them. Iterate.
I have adapted to an Agile Framework for most of my life tasks. Break the work into manageable chunks - it makes you feel more successful. You can get two big things done today or 10 little things. 10 is better. 10 feels accomplished. I am also a fan of the 80/20. Get the room painted. Touch up the trim next weekend. 80/20.
He likes the view. |
This all goes really well when requirements are clear and well defined.
I've not had a wife for very long but I do know, from my own experience, that a happy wife makes for a happy life. I desire both of those things.
So, today when I got a text asking me to put the Halloween skeletons in the garage rafters after work, I happily complied with a 'Happy to'.
Problem statement: The Halloween skeletons need to be put away.
Initial Requirement: Put the skeletons in the garage rafters.
Now, it's kind of clear, but not crystal. I wasn't given exact specs of where to put them. That part is what feeds my creativity. How can I solve this in a way that makes me feel creative and solves the problem?
Will we hear screaming from the children when they go get their bikes out of the garage?
Likely.
Is the problem statement solved?
Yep.
Am I likely to forget and scare myself at some point?
Also, yep.
Greetings. |
No comments:
Post a Comment