Can't wait to try this! I used miro.com in the past but it has a paywall. Congrats on the launch.
Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
11–20 of 28 posts
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#12I'm curious, is there a featmap for featmap? :)
The most requsted feature is integration with GitHub. What do you think it is missing?
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#13So... 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.
Actually, no. It is far less robotic in practice and works quite well because once the schedule is better known and controlled, developers can go home on time every day. The whole crunch mode thing is effectively eliminated.
Pivots get into work at the same time, work together all day and then get to leave at the exact sane normal 8 hour work day. Every single day. Sounds like a great job to me.
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#14Earlier quoted context omitted.
"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.
Actually, no. It is far less robotic in practice and works quite well because once the schedule is better known and controlled, developers can go home on time every day. The whole crunch mode thing is effectively eliminated. Pivots get into work at the same time, work together all day and then get to leave at the exact sane normal 8 hour work day. Every single day. Sounds like a great job to me.
20 'points' (whatever they are) last week has zero bearing on what will be accomplished this week, or next or in 6 months time. Vanity metrics. Your silently forcing them to be a feature factory and act in a consistent robotic fashion no matter what the problem at hand is. I bet your tech debt velocity is increasing weekly.
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#15Just a thought:
I tried using the demo on mobile and it was easy to accidentally reorder/reorganize tasks.
Perhaps place an undo button nearby or somehow decrease touch sensitivity without removing functionality?
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#16Awesome - 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 li…
Cool, let me know how it went with the client!
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#17Thanks! Seems very useful and clean enough to inform stake holders and the entire team.
My idea is that the tool can be used to quickly communicate product vision and current progress to the team or external stake holders. I can also imagine teams using it as their primary tracking tool, if the company is small enough. If you end up using it, please let me know how I can improve it and how you are using it.
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#18Can't wait to try this! I used miro.com in the past but it has a paywall. Congrats on the launch.
Thanks! I know that Featmap is not unique in the space, there are a lot of similar products. What I was missing was a free and open sourced tool with just the right feature set. After a couple of months of ambivalence, I decided to scratch my own itch. Would love to get your feedback once you've tried it.
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#19Just a thought: I tried using the demo on mobile and it was easy to accidentally reorder/reorganize tasks. Perhaps place an undo button nearby or somehow decrease touch sensitivity without removing functionality?
To be honest, I haven't paid much attention to mobile - mostly because I am nearly always on a desktop. Obviously a large screen is better when you are making changes to a big story map, but I get your point. Thanks for the detailed feedback, it really means a lot to me.
Re: Show HN: Featmap – a user story mapping tool built with Go, React and TypeScript
#20Earlier quoted context omitted.
"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.
Actually, no. It is far less robotic in practice and works quite well because once the schedule is better known and controlled, developers can go home on time every day. The whole crunch mode thing is effectively eliminated. Pivots get into work at the same time, work together all day and then get to leave at the exact sane normal 8 hour work day. Every single day. Sounds like a great job to me.
If a team is great at pointing, and the lead/PM is good at scoping then I tend to agree with this.
I've seen 1 team good enough at pointing to do 2 week Sprints, call their velocity, and generally nail it.
It was a small federal team on a mature (7 year old) coldfusion application with a backlog that mainly involved minor features and bug fixes, where the app had a narrow clear scope.
The startups I've been involved in are too chaotic. When you have a team lead or project manager who never met a feature request they could say "no" or "that's not urgent" too, the problem is even worse. Also when your domain or features are generally not well defined "let's bolt a full CRM onto this now"
Among the chaos, I still go home on time every day.