New answers tagged

0

I often see teams using both a top-down and a bottom-up approach at the same time. But, then again, maybe I'm using the term "bottom-up" in a slightly different way. "User stories," to me, are top-down: "this building is going to have a magnificent stone archway over the front entrance." But someone's also at the same time ...


1

A really fun way is doing a Design Sprint. Followed by some Impact mapping and User story mapping. Depending on your product get out of the freaking building and let the developers talk to actual users. Maybe research the Shiftup program to help you facilitate continuous innovation. Bring the team together with the users and key-stakeholders, get and keep ...


1

As mentioned in other answers, you can go for story mapping exercise but first you may consider aligning all stakeholders to a prioritisation framework and high level objectives/ themes/ Epics (for the product you are building). The main problem with the bottom-up approach is the divergence of ideas from different individuals which may or may not be aligned ...


Top 50 recent answers are included