Feature gluttony is a common sin among IT projects. Customers deliver never ending wish list of features they want. However, the key is not to build everything, but only things that are really needed. Learn how to defeat feature gluttony by: - setting common aim - defining most important use cases - defining critical process from the business perspective - decide what should be delivered first … and build excellent piece of software :)

2. how to defeat feature
gluttony
Mrowca Katarzyna

3. <me>
</me>

4. why should we care?

5. Source: http://geek-and-poke.com/
I love SAP
HR
Because it shows
you that there is
software even
worse than ours?
Just
because

6. source: http://futureblog.pl/wp-content/uploads/2011/12/dieta2.jpg
gluttony

7. Source: http://www.pusheen.com/

8. Source: http://9gag.com/

11. why it is bad?

12. pareto rulepareto rule

13. complexity

14. usability

15. happiness

23. Source:
http://brentblog.typepad.com/brentblog/2006/02/features_and_us.html

24. keep it lean

25. how?

26. rule 1: team

27. don’t try to teach
„business” to do business
rule 2

28. they are experts!
http://youtu.be/BKorP55Aqvg

29. rule 3: common aim

30. how to keep it simple?

31. define the most important
business processes
step 1

32. define use cases
step 2

33. decide how to measure
step 3

34. summary

35. summary

36. summary

37. summary

38. summary
key business process
use cases
measurement

39. summary
key business process
use cases
measurement

40. summary
key business process
use cases
measurement

41. it‘s easy to add a feature

42. it‘s hard to make the app simple

43. Questions?
http://geek-and-poke.com/