http://tynerblain.com/blog/2005/12/08/it%e2%80%99s-not-business-it%e2%80%99s-just-personal/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 http://tynerblain.com/blog/2005/12/08/it%e2%80%99s-not-business-it%e2%80%99s-just-personal/comment-page-1/#comment-131 Top five presentation tips --Tyner Blain Mon, 23 Jan 2006 19:26:32 +0000 http://tynerblain.com/blog/2005/12/08/it%e2%80%99s-not-business-it%e2%80%99s-just-personal/#comment-131 [...] Know your audience. A key preparation - you have to have a goal for a presentation. Are you convincing, educating or inspiring people? What do those people care about (and what do they already know?)?  Also - do you actually know the people in the audience? [...] [...] Know your audience. A key preparation – you have to have a goal for a presentation. Are you convincing, educating or inspiring people? What do those people care about (and what do they already know?)?  Also – do you actually know the people in the audience? [...]

]]> http://tynerblain.com/blog/2005/12/08/it%e2%80%99s-not-business-it%e2%80%99s-just-personal/comment-page-1/#comment-105 Tyner Blain » Prioritizing requirements - three techniques Thu, 19 Jan 2006 05:02:47 +0000 http://tynerblain.com/blog/2005/12/08/it%e2%80%99s-not-business-it%e2%80%99s-just-personal/#comment-105 [...] The second real-world consideration is the executive whim - there are often personal agendas, political pressures, and perceptions held by the stakeholders that will create pressure to implement some features with low intrinsic value ahead of some features with higher value. While people may optimize by nature, it isn’t always the company’s bottom line for which they are optimizing. Try and work with these people to prioritize the high value features first. Be compelling. It may be that there are tactical considerations (the CEO may demand that the website match corporate look and feel standards before it allows for new order submission), and the funding for the project may be dependent upon addressing someone’s pet peeve in the first release. We just have to do it some times. [...] [...] The second real-world consideration is the executive whim – there are often personal agendas, political pressures, and perceptions held by the stakeholders that will create pressure to implement some features with low intrinsic value ahead of some features with higher value. While people may optimize by nature, it isn’t always the company’s bottom line for which they are optimizing. Try and work with these people to prioritize the high value features first. Be compelling. It may be that there are tactical considerations (the CEO may demand that the website match corporate look and feel standards before it allows for new order submission), and the funding for the project may be dependent upon addressing someone’s pet peeve in the first release. We just have to do it some times. [...]

]]>