New ask Hacker News story: Ask HN: From idea to feature – how does your agile process look like?
Ask HN: From idea to feature – how does your agile process look like?
2 by rainerzufall | 0 comments on Hacker News.
Hey HN! Long time lurker here. I'm really interested in how your agile workflow looks like. I've never had a single project that wasn't a clusterfuck. Features generally look like: "Let's do X" without any thoughts about UX, side effects etc. thats all done on the fly while implementing the stories of the feature. A lot of the time you start stories just to stop it in the middle because there are some sort of blockers. In my ideal world the process should look like this: 1. start with an idea that is backed by actual user feedback, an assumption based on your personas that you can validate afterwards or a business requirement. 2. plan out the idea. Have discussions about nfr's / technical requirements, add wireframes / ux concepts, have concrete goals (what problem do you want to solve). At this stage there also could be some user stories / tasks (rough stage) to the feature / idea. 3. the feature is now "ready for dev" But in reality this is rarely the case. Is this an organizational problem (and i was just unlucky with all the organizations i worked for)? If it is an organizational problem: How does your process look like and what tools do you use along the way? Cheers!
2 by rainerzufall | 0 comments on Hacker News.
Hey HN! Long time lurker here. I'm really interested in how your agile workflow looks like. I've never had a single project that wasn't a clusterfuck. Features generally look like: "Let's do X" without any thoughts about UX, side effects etc. thats all done on the fly while implementing the stories of the feature. A lot of the time you start stories just to stop it in the middle because there are some sort of blockers. In my ideal world the process should look like this: 1. start with an idea that is backed by actual user feedback, an assumption based on your personas that you can validate afterwards or a business requirement. 2. plan out the idea. Have discussions about nfr's / technical requirements, add wireframes / ux concepts, have concrete goals (what problem do you want to solve). At this stage there also could be some user stories / tasks (rough stage) to the feature / idea. 3. the feature is now "ready for dev" But in reality this is rarely the case. Is this an organizational problem (and i was just unlucky with all the organizations i worked for)? If it is an organizational problem: How does your process look like and what tools do you use along the way? Cheers!
Comments
Post a Comment