On 13 March 2012 01:27, David Zinman wrote: >> I don't like adding new terminology. A blueprint should be achievable >> in a month and should be used instead of work item blocks. Work >> packages can be blueprint headlines - it doesn't matter that these >> will be refined and perhaps split into the final blueprints as long as >> there is tracability. > > I'm fine with that. My attempt was to differentiate a bit between > the higher level description of the work in Papyrs and the detailed > work items described in blueprints in order to avoid redundancy. If > there is consensus I will change the template label to "Blueprints". >
It seems redundant to me. A blueprint contains a higher level description and the detailed work items to do. I'll prefer to to link the operational/agile plan items to a blueprint when applicable. _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
