Live data from Hacker News

Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

github.com

1–10 of 28 posts

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#3
post #2

Looks very nice. I would use Trello for this normally as it does the job good enough. This seems like a more specific service. I am curious how many ppl will choose this instead and for what reasons.

Trello is often good enough. With Featmap, I wanted to create the user story mapping tool that is juuust perfect for my use cases. Hopefully, other people will also find it useful!

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#4
Awesome - it happened I was exactly thinking about a tool like this when on a long meeting call today.

I have clients that refuse to use another tool, refuse another sign up in their email account . In the same time those clients are mostly chaotic to unorganized and we tend to repeat the same points over and over again in the course of a year until all points are fulfilled (web platform dev work).

This tool seems like the just Trello enough for ONE single view - no explanation to give - will try this from next week's meeting call on

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#6
So... the reason why Pivotal Tracker is still my favorite tool is because most PM's want to know when a feature is going to be done. With PT, developers assign points to stories and the 3 week average (customizable) is what makes a velocity.

If velocity is 20, then 20 points worth of stories fit into an iteration (week). Points include testing, so that isn't cut out, like with sprints. As a PM, I can get developers to point stories out for a few weeks worth of iterations. If I need to move stories around, I can do that easily and I can see how moving things around affects 'when it will be available'.

If I was going to use another tool, I'd want PT's 'velocity' as a base feature for sure.

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#7
post #6

So... the reason why Pivotal Tracker is still my favorite tool is because most PM's want to know when a feature is going to be done. With PT, developers assign points to stories and the 3 week average (customizable) is what makes a velocity. If velocity is 20, then 20 points worth of stories fit into an iteration (week). Points include testing, so that isn't cut out, like with sprints. As a PM, I can get developers t…

I don't think tools like this are meant to replace Pivotal (or Jira, or whatever you use for tracking Sprint stories/tickets).

Roadmapping (or in this case, user story mapping) is usually done independently from Sprint planning as a way to develop and share the product roadmap so that your team can prioritize Jira/Pivotal tickets or whatever your team uses for tracking Sprint tasks.

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#9
post #6

So... the reason why Pivotal Tracker is still my favorite tool is because most PM's want to know when a feature is going to be done. With PT, developers assign points to stories and the 3 week average (customizable) is what makes a velocity. If velocity is 20, then 20 points worth of stories fit into an iteration (week). Points include testing, so that isn't cut out, like with sprints. As a PM, I can get developers t…

"If velocity is 20, then 20 points worth of stories fit into an iteration" -> When was software engineering so regimented, predictable and precise. This sort of mentality treats engineers as robotic and is a cancer in the industry currently.

Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript

#10
post #7
post #6

So... the reason why Pivotal Tracker is still my favorite tool is because most PM's want to know when a feature is going to be done. With PT, developers assign points to stories and the 3 week average (customizable) is what makes a velocity. If velocity is 20, then 20 points worth of stories fit into an iteration (week). Points include testing, so that isn't cut out, like with sprints. As a PM, I can get developers t…

I don't think tools like this are meant to replace Pivotal (or Jira, or whatever you use for tracking Sprint stories/tickets). Roadmapping (or in this case, user story mapping) is usually done independently from Sprint planning as a way to develop and share the product roadmap so that your team can prioritize Jira/Pivotal tickets or whatever your team uses for tracking Sprint tasks.

Yes, Pivotal model (disclosure, I worked at Pivotal/CloudFoundry for a bit) just uses sticky notes and they do this in an 'inception'.

https://content.pivotal.io/blog/inception-knowing-what-to-bu...

Sticky notes are something more dynamic and hand writing things out makes you think more about things than just filling out boxes on a screen. It also allow you to iterate quickly and just toss the ideas you don't like into a corner.

Those stickies turn into 8 point (or unpointed) stories, put into Tracker, which then get broken down into smaller stories which can be discussed (iteration planning meetings) tasked out and worked on.

So yea... I guess if someone made me use a tool like this over simple sticky notes, I'd probably be really frustrated at the end of the day.

Post reply on HN