On Wed, Aug 24, 2011 at 3:48 AM, Paul Larson <[email protected]> wrote: > What about this: > Split the blueprint into an implementation blueprint, and an upstreaming > blueprint (if needed) that are dependencies of a tracking blueprint for the > thing you are trying to implement and move upstream (more could be added if > further dependencies are needed, and warrant having a blueprint to track the > tasks for them). This way you could estimate the pieces one chunk at a > time, and take your best guess on when to target the tracking blueprint for > the whole thing.
No, it's too much overhead. Does the extra work in splitting give enough extra visibility and value to justify the engineers time and (IMO) bad will from this extra work? Half of the GCC blueprints would need to be split... -- Michael _______________________________________________ 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
