project management - How to prioritize future features (enterprise web development) -
suppose you're product manager internal enterprise web application has 2000 users , 7 developers. have list of 350 future features, each ranging 5 150 developer days of work.
how choose features work on, , how run release process?
here's i'm thinking: (skip if boring)
release process. work on several features @ once, release each individually when it's ready. other option (what we've been doing point) pick out set of features, designate them "a release", , release them @ once (announcing via mass email).
the advantage of shorter release process can release features finish development. advantage of bigger process it's easier organize.
feature prioritization. put future features in spreadsheet columns feature, description, comments, estimate, benefit, (your) estimate, (your) benefit. give copies 2 senior engineers, other senior project manager , yourself.
the engineers estimate features (how precisely? consulting each other?). determine benefit, allocates points (total = 10 * [number of future features]) among future features (without consulting each other?), compare scores , average (?).
another potential strategy here rank each feature on absolute (say) 1-100 scale. having absolute ranking nice because makes prioritizing our feature list changes easier (we don't want have redistribute points every time proposes new feature).
what's strategy? books / websites attack problem @ level of detail?
there's great book helps cover topic called agile estimating , planning mike cohn. has great ways estimate , plan releases. including planning game called planning poker engineering team gets cards estaimate user stories. each engineer plays card 1,2,3,5,8,13 face down. high , low card explains , again. after 1 or 2 repeats there convergence on same estimate.
there's beyond software architecture: creating , sustaining winning solutions luke hohmann might of product management related pieces , reasoning use prioritization. have not yet read book went talk luke hohmann covered subjects of book , can't wait read it.
also recommend reading books on various agile development processes such scrum, crystal clear, , xp. there's agile project management scrum ken schwaber , crystal clear: human-powered methodology small teams alistair cockburn. extreme programming explained: embrace change (2nd edition) kent beck , cynthia andres.
as feature prioritization, done stakeholders. need work on features address needs of stakeholders, which, luke hohmann points out, includes system architecture.
however, 1 of important things make sure have agreement on software development process team. if force process , team doesn't believe in, not work.
Comments
Post a Comment