Comments on: APR: Prototype Update http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/comment-page-1/#comment-93955 Scott Sehlhorst Fri, 04 May 2007 19:33:28 +0000 http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/#comment-93955 Implemented it. I created six categories to start with: # Define existing categories Category.create :name => 'Product Management' Category.create :name => 'Business Analysis' Category.create :name => 'Project Management' Category.create :name => 'Testing' Category.create :name => 'Agile Development' Category.create :name => 'Interaction Design' I think that will get us started. Need to do a little bit of presentation/cleanup, and then deploy the site. Implemented it. I created six categories to start with:
# Define existing categories
Category.create :name => ‘Product Management’
Category.create :name => ‘Business Analysis’
Category.create :name => ‘Project Management’
Category.create :name => ‘Testing’
Category.create :name => ‘Agile Development’
Category.create :name => ‘Interaction Design’

I think that will get us started. Need to do a little bit of presentation/cleanup, and then deploy the site.

]]> By: Rolf http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/comment-page-1/#comment-93835 Rolf Fri, 04 May 2007 06:49:17 +0000 http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/#comment-93835 1 article in 1..* categories: definitely. For similar problems, I tend to have fixed lists of categories, as long as there is a way to change the list. 1 article in 1..* categories: definitely.
For similar problems, I tend to have fixed lists of categories, as long as there is a way to change the list.

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/comment-page-1/#comment-93833 Scott Sehlhorst Fri, 04 May 2007 06:36:50 +0000 http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/#comment-93833 Heh. Just finished the prototype implementation of ratings (you can make them, the article score is the average of all ratings made by users on the article). I should be able to get categories implemented with a fixed list. Then I need to update the views for (latest, highest scoring) and filtering by category. I think an article should be able to be in multiple categories. Thoughts? Heh. Just finished the prototype implementation of ratings (you can make them, the article score is the average of all ratings made by users on the article).

I should be able to get categories implemented with a fixed list. Then I need to update the views for (latest, highest scoring) and filtering by category.

I think an article should be able to be in multiple categories.

Thoughts?

]]> By: Rolf http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/comment-page-1/#comment-93823 Rolf Fri, 04 May 2007 05:57:58 +0000 http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/#comment-93823 I realize that we are not very far into the product (it's the first prototype), but I still think that ratings should be postponed to 'after comments'. Just for the sake of the priorities which were set by the voting on the use cases. If you think about the ratings as something more complex to display than an unordered list, something that is more exiting for the prototype users, I suggest to use 'areas' for this purpose. Again, because of the primary use cases. However, what do you think about a first prototype w/o ratings and w/o comments? Suggesting arcticles and browsing areas are the main use cases, so we should first check that. I'm referring to the Eliminate Waste principle of Mary Poppendieck's Lean Software Development (I see that ratings are not a waste in general, but maybe as of now). I realize that we are not very far into the product (it’s the first prototype), but I still think that ratings should be postponed to ‘after comments’. Just for the sake of the priorities which were set by the voting on the use cases.
If you think about the ratings as something more complex to display than an unordered list, something that is more exiting for the prototype users, I suggest to use ‘areas’ for this purpose. Again, because of the primary use cases.
However, what do you think about a first prototype w/o ratings and w/o comments? Suggesting arcticles and browsing areas are the main use cases, so we should first check that. I’m referring to the Eliminate Waste principle of Mary Poppendieck’s Lean Software Development (I see that ratings are not a waste in general, but maybe as of now).

]]> By: Roger L. Cauvin http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/comment-page-1/#comment-93729 Roger L. Cauvin Thu, 03 May 2007 18:35:15 +0000 http://tynerblain.com/blog/2007/05/02/apr-prototype-update-2/#comment-93729 Moving along nicely. It's probably more consistent with agile to write tests before code, so you might try reversing the order of those two items in your refactoring process. Moving along nicely. It’s probably more consistent with agile to write tests before code, so you might try reversing the order of those two items in your refactoring process.

]]>