Recent searches
Search options
I recently came across the #RICE prioritization model that product managers can use to set goals and prioritize whats important.
I felt that this could be interesting to map over on how the #softwareengineering teams set goals and prioritize what is important as we build software, but within that context.
1/*
For example, a smaller team after introspection may come to a conclusion that they spend too much time on review stage with a lot of back and forth.
Therefore a wildly important goal (WIG in RICE) could be to decrease that time with some way. This is roughly and possibly easily observable and the performance of different solutions to that can be measured by today's tools, like to watch review time after applying X solution that helps decrease review time.
2/*
What I would be interested to hear from people is their opinion and what is the process that they follow or have followed in the past to keep evolving and growing the knowledge of a team or directing and focusing the team on the important things for the business or even for the software engineering process as well.
@thgs
Two concepts I pay attention to are 1) What is the "low hanging fruit", so we can see results early? 2) What is actually making life harder than it should be, so we don't have GIGO?
Start with visiting these questions regularly and recording progress, but: #1 can fail because of poor decision making, analysis-paralysis and unwillingness to experiment; #2 can fail because of lack of self-monitoring, self-analysis and thinking independently of what the management is feeding you.
@orchun yes, thank you. That helps.
The revisiting part is actually a part of RICE I believe so yes, that is included in the model anyway.
Also mentioning GIGO, makes a lot of sense. Kind of clicked in my mind after your comment.