Project Selection Process

This topic has 2 replies, 3 voices, and was last updated 12 years, 6 months ago by j.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts
October 27, 2009 at 11:44 pm #26880

Kurt
★ 10 Years ★
Participant

@Kurt Include @Kurt in your post and this person will
be notified via email.

Please suggest steps and appropriate tools for a newly forned selection committee to quickly learn enough about proprosed improvements initiatives to be in a position in a short amount of time to rank and proiritize those projects.

0

November 2, 2009 at 4:45 am #65344

Abhishek Ramavat
★ 10 Years ★
Participant

@Abhishek-Ramavat Include @Abhishek-Ramavat in your post and this person will
be notified via email.

Hi Kurt,
Any project selection should be based on business objectives. Identify keys issues related to customer satisfaction, efficiency and defect/errors. You can prioritize using a simple approach of Kano need analysis i.e. meeting implied & stated and then providing delighters to stakeholders. This should follow a logical sequence of meeting implied needs first and then focusing on stated needs and delighters.
Hope this helps.
Abhishek

0

November 4, 2009 at 10:13 am #65346

j
★ 10 Years ★
Participant

@j Include @j in your post and this person will
be notified via email.

A C&E can work nicely with projects down the left and business voice/goals/needs along the top.

0
Author

Posts

Viewing 3 posts - 1 through 3 (of 3 total)

The forum ‘Software/IT’ is closed to new topics and replies.