Based on past experience, it's probably a good idea to draft up the
workflows independent on understanding the engineering costs. It
helps us figure out what is essential and what is not as well as
which scenarios. It really helps to come into the engineering
discussions with a thorough understanding of this.
I guess what I am saying is that I don't need to have any engineering
swags to do this piece.
Cheers,
Sheila
On Mar 29, 2007, at 12:21 PM, Priscilla Chung wrote:
I don't think that we'll actually be able to completely SWAG this
today. As responses to the thread show, we still have some
uncertainty about what is in or out, and regarding the scope of
what is in.
I think there is a little bit of a chicken and an egg thing going
here. I think we know there is a lot of features for dashboard, but
we need to understand how long things will take to be able to tease
out the essential features. Then work out workflow to understand
what the expectations are from a user's perspective.
Also, Matthew is going to need a bit of time get this all worked
out. I don't want us to have unrealistic expectations about what
is going to get done today.
That's fine. What do you suggest we do in today's meeting then? Or
are you saying it's not worth meeting until Matthew has a chance to
review what all the features are.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
