bdehaaff

49 ms·

481.
by bdehaaff 13y ago
You touch on another interesting area. How to rank the importance of features. I am careful to highlight our own work, but do a search for Aha! Scorecards and Aha! Scores. We introduced a way for teams to enter into their account their own
482.
by bdehaaff 13y ago
Totally agree. The challenges are multi-faceted, but one of the biggest issues is that it's not for deciding the "whys" or "whats." Why we are doing something is strategy and what and when we are going to deliver is
483.
by bdehaaff 13y ago
Thanks for the comment. The point is that using Kanban or implementing "agile" is not a savior from the engineering death spiral. The post includes that exact point in the first paragraph.
484.
by bdehaaff 13y ago
Great insights. Give the folks who can get the work done the freedom and responsibility to get the work done. Managers should remove barriers -- not impose additional ones ever time something goes wrong. It's hard enough to build great
485.
by bdehaaff 13y ago
Great. Thanks for sharing this success story. It would be interesting to know if the engineering team is motivated and understands the why they are building what they are.
486.
by bdehaaff 13y ago
Kanban does nothing to solve the product strategy and market fit questions and is often applied as a fix-all for much deeper rooted problems. I would also argue that Kanban has the tendency to turn engineers into widget builders and is demo
487.
by bdehaaff 13y ago
True. That's one of the ways that you end up in this engineering death spiral -- bad market / product fit and thrashing strategy.
488.
by bdehaaff 13y ago
Yep. Big change is needed one way or another because the ground is approaching faster than most teams in the death spiral think.
489.
by bdehaaff 13y ago
I love the honesty of this story and I wish it were told more often. I just kept nodding. You did touch on one concept that I almost added to the piece... "we always do it like that". If this post continues to grow in popularity I
490.
by bdehaaff 13y ago
Exactly. Put the folks who can get the work done in charge of actually getting the work done. Give them the responsibility and allow their courage to flourish 9and remove barriers when needed). Celebrate their accomplishments.
491.
by bdehaaff 13y ago
Yes, I think you are saying that the focus needs to be on results. Not effort. I agree, but is that what you are highlighting with your comments?
492.
by bdehaaff 13y ago
It's been fixed.
493.
by bdehaaff 13y ago
Thank you for pointing that out. Grateful for the call out. Best.
494.
by bdehaaff 13y ago
Very true. There is always some new "fix it." The problem is often that the engineering tools do not improve product management in the least and if the product strategy is bad and customer understanding is missing, no engineering
495.
by bdehaaff 13y ago
Personal experience after being an early employee or founder of six software companies and knowing or speaking directly with folks in hundreds of others. Simple experience and pattern recognition. Not science.
496.
by bdehaaff 13y ago
Thanks. The point is that applying simple tools like Kanban or trying to "shock" the system by "becoming" agile typically does not work because these tools do not address the underlying issues.
497.
by bdehaaff 13y ago
Well said. I totally agree. Sometimes it's just a blip and sometimes there is distrust and structural dysfunction that is going to need a lot of work to fix.
498.
by bdehaaff 13y ago
I have seen a turnaround, but it usually takes significant change. And typically that means management change. How long have you been experiencing the problem? The longer it goes on the harder it is to escape.
499.
Kanban can not save you from the engineering death spiral(blog.aha.io)
60 points by bdehaaff 13y ago|64 comments
500.
The Engineering Death Spiral(blog.aha.io)
2 points by bdehaaff 13y ago|1 comments
501.
The Lean(est) Startup(blog.aha.io)
1 points by bdehaaff 13y ago|0 comments
502.
Ask HN: What does being Agile mean to you?
1 points by bdehaaff 13y ago|0 comments
503.
$0 - $200M in nine months [Startup lessons](blog.aha.io)
1 points by bdehaaff 13y ago|0 comments
504.
A Better Product Backlog(blog.aha.io)
2 points by bdehaaff 13y ago|0 comments
505.
by bdehaaff 13y ago
Thanks. I always take any kind words I can get on HN. What do you mean by trolling? It's meant to be good-humored, but there are definitely some crazy annoying "sayings" on the list.
506.
20 Things Developers Should Stop Saying(blog.aha.io)
2 points by bdehaaff 13y ago|3 comments
507.
Automatically Import Features From Jira into Aha for Roadmap Planning(blog.aha.io)
1 points by bdehaaff 13y ago|0 comments
508.
Is there a better way to build software than the MVP?(quora.com)
2 points by bdehaaff 13y ago|0 comments
509.
Capacity planning isn't sexy -- but we all do it(blog.aha.io)
1 points by bdehaaff 13y ago|0 comments
510.
Mindjet and Spigit Merge to Advance Business Innovation(mindjet.com)
1 points by bdehaaff 13y ago|0 comments

More ›