http://blog.letmego.com/2009/02/letmego-has-146-documented-use-cases-here-is-one/ Wed, 07 Dec 2011 16:45:04 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://blog.letmego.com/2009/02/letmego-has-146-documented-use-cases-here-is-one/comment-page-1/#comment-49085 Job Opening: Coding Ninja (Full Time Web Developer) « inbed.me blog Thu, 29 Sep 2011 20:00:14 +0000 http://alextorrenegra.wordpress.com/2009/02/12/letmego-has-146-documented-use-cases-here-is-one/#comment-49085 [...] Only coding features that have been documented already using detailed use cases and wireframes (This will reduce your anxiety level. To learn more about the way we document use cases read this post). [...] [...] Only coding features that have been documented already using detailed use cases and wireframes (This will reduce your anxiety level. To learn more about the way we document use cases read this post). [...]

]]> http://blog.letmego.com/2009/02/letmego-has-146-documented-use-cases-here-is-one/comment-page-1/#comment-1293 Letty Brach Mon, 28 Jun 2010 22:11:24 +0000 http://alextorrenegra.wordpress.com/2009/02/12/letmego-has-146-documented-use-cases-here-is-one/#comment-1293 This is a very awesome blog , how do i subscribe to your newsletter ? This is a very awesome blog , how do i subscribe to your newsletter ?

]]> http://blog.letmego.com/2009/02/letmego-has-146-documented-use-cases-here-is-one/comment-page-1/#comment-46 Alberto Dominguez Thu, 12 Feb 2009 17:03:00 +0000 http://alextorrenegra.wordpress.com/2009/02/12/letmego-has-146-documented-use-cases-here-is-one/#comment-46 I do believe that Agile Development is good enough for small groups -as you posted few days ago, small groups will be able to innovate and adapt faster than bigger groups. Not sure why, but that's the way it is.However I disagree about your point of user stories and use cases. As we discussed few days ago, Use Cases can support User Stories. It is easier for non technical people and new developers -that could be part of the team in the future- to read what is the "story" behind the system. Just like you do when you are in a meeting and start explaining about the functionality of the system. However formal documentation should be linked to those "nice to understand" stories -i.e. Use Cases!It is about perception, your UC has a "Usage Narrative" that is almost a "User Story" I do believe that Agile Development is good enough for small groups -as you posted few days ago, small groups will be able to innovate and adapt faster than bigger groups. Not sure why, but that’s the way it is.However I disagree about your point of user stories and use cases. As we discussed few days ago, Use Cases can support User Stories. It is easier for non technical people and new developers -that could be part of the team in the future- to read what is the “story” behind the system. Just like you do when you are in a meeting and start explaining about the functionality of the system. However formal documentation should be linked to those “nice to understand” stories -i.e. Use Cases!It is about perception, your UC has a “Usage Narrative” that is almost a “User Story”

]]>