What is Reddit's opinion of
User Story Mapping: Discover the Whole Story, Build the Right Product?
From 3.5 billion Reddit comments
By popularity on Reddit, this product is:
10 reviews of this product found across Reddit:
You could read User Story Mapping. That's canon for PMs.
But I think you should focus your energy differently. Don't come in trying to fool people about the imposter syndrome. They hired you, and trust me you didn't fool them. I would lean into your noob-ness and play that new guy/girl card for a while.
Spend as much as time as possible using the product. Ask as many stupid questions as you possibly can. Become the smartest and most educated user of your product that there is. Go through all of the defect tickets in your backlog. Talk to as many users as possible. If you were to spend the first 30-60 days just doing that then I feel you would be viewed as a superhuman product manager. Come up with your own top issues list of what you would go fix first if you could (plot twist: you can).
Great Product Managers have a strong point of view about the roadmap for their product. The only way to develop that point of view is to use the product and talk to the users.
I would recommend Jeff Patton's book on story mapping. It's a very simple yet powerful technique on mapping out the requirements and slicing them into releases.
Thanks.
>Jeff Patton’s User Stories
This one ?
The system itself works, it does pretty much exactly what we need it to, constraints, well the only real constraint I can see is lack of motivation at board level to make changes, that and the CRM is very, very deeply integrated in to our website and other applications that we use.
As far as technical debt is concerned, it's similar, but kind of in reverse, we started out with a barebones architecture and built, at great cost both financially and with regards to time a new system, when an OTS solution would have done the job just as well if not better and would have still provided a degree of flexibility, likely enough to make changes as time progressed and needs changed.
I've instigated the use of a cloud-based Kanban board and the backlog has now been prioritized (there's items on there that are a year past-due and we've seen nothing of them) and loaded to that and the team and contractor are now largely on board, we now just need to sit down agree sprints and work on reviewing submitted work, whereas at the moment, the contractor gets given a not-always-detailed brief and comes back months later with something that doesn't reflect what was visualized at the outset.
Ultimately though, I'm really looking at the best ways for me to improve my own understanding of Agile and project management in general, with a view to apply it more in my current role, and also, potentially look it is a career move.
Very very very quick rundown:
Numerous independently created lightweight development methodologies appeared in the 80s & 90s to address the problems the authors saw with the methods used by most companies. The creators of each methodology realized each had its unique merits but also had shared core goals and frequently shared backgrounds. Those shared goals are what became the Agile Manifesto, a set of 4 values and 12 principles.
Start by reading this: Modern Agile. It is an updated version of the agile manifesto that reduces it to just 4 easy principles ~~of $29.95~~... I mean, easy principles to follow:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
Then consider how anything being done, currently or proposed, lines up with those principles. The Modern Agile site also has some suggestions on reading materials and other things that could benefit you.
Getting in more detail than that is going to be a little tougher as I don't know about the particular practices you're following. But I can offer a couple good general tips.
First, join an agile meetup. Really. Hearing people's issues & solutions first hand, and sharing your own is hands-down the best way to learn about Agile & keep up to date on what is going on in the Agile world. Reddit is cool, but in-person is best.
Next, learn about whatever overarching process(es) the team & company are using: Scrum, Kanban, XP, etc. The basics of each tend to be pretty quick reads and provide information on their background.
Finally, start delving into common Agile practices, of course focusing on the ones your company is already using first: User Story writing & mapping, swarming, backlog prioritization tips, planning, scaling agile, etc.
You’re at the beginning of a long road.
User stories are part of story mapping. With our understanding how the piece fits into the whole you can waste a lot of time and money.
Then understand what you need them to build. Try to make sure you have wireframe and understand the user experience. Work with engineering leads to sort out the engineering solution. Collaborate with your team to break it down into manageable chunks and start from there.
Start with this book
User Story Mapping: Discover the Whole Story, Build the Right Product https://www.amazon.com/dp/1491904909/ref=cm_sw_r_cp_api_glt_i_TCFZ6A84YCSVTMQ1QC6A
Here’s a decent video
Don’t know why you got downvoted, it’s a relevant question
Good starting point here
User Story Mapping: Discover the Whole Story, Build the Right Product https://www.amazon.com/dp/1491904909/ref=cm_sw_r_cp_api_glt_fabc_WS54BFDTDSPJT6NBF53T
Watch Product Ownership in a nutshell - https://www.youtube.com/watch?v=502ILHjX9EE
Read Product Mastery (Geoff Watts) - https://www.inspectandadapt.com/product/product-mastery
and maybe User Story Mapping (Jeff Patton) - https://www.amazon.co.uk/User-Story-Mapping-Discover-Product/dp/1491904909
Take your time looking around for courses. Theres some great stuff out there by Geoff Watts, Marty Cagan, Jeff Patton & Roman Pichler (and many others!)
It sounds like you need a user story map. Start here: https://www.jpattonassociates.com/story-mapping/. If this is resonating, read his book: https://www.amazon.com/dp/1491904909/.
First find yourself an awesome Scrum Master. They are a key to you being an awesome PO.
Second read User Story Mapping by Jeff Patton. https://www.amazon.com/dp/1491904909/ref=cm_sw_r_cp_awdb_t1_eAm-DbP113649
Popular alternatives to User Story Mapping: Discove...
Clean Code: A Handbook of Agile Software Craftsmanship
Code: The Hidden Language of Computer Hardware and Software
