With relief, both of my current project teams are keen as mustard to take on keynoting. One hasn't even started a specification, not even in draft, so the other is flying ahead - using them for even pre-details annotation (nice).
BUT
The other team (without the spec.) are a bit more cautious, and are looking to it's adoption in later stages of detailing - and we had a quick review of "next steps" today and a absolutely sound question got raised (in response to my, "lets not use text yeah?")... you ready for it?
"If we can't use text, how do we write construction notes in my details on a need-by-need basis, because the specification driven keynote won't capture that"
...to which I, foolishly, said "Easy. We can add an instance-based text parameter for comments".
Only to subsequently learn. We can't. Or at least, I can't. Can we?
Has anyone worked out a way to get the keynote tag saying anything more than the default "Value" & "Description" ?
BUT
The other team (without the spec.) are a bit more cautious, and are looking to it's adoption in later stages of detailing - and we had a quick review of "next steps" today and a absolutely sound question got raised (in response to my, "lets not use text yeah?")... you ready for it?
"If we can't use text, how do we write construction notes in my details on a need-by-need basis, because the specification driven keynote won't capture that"
...to which I, foolishly, said "Easy. We can add an instance-based text parameter for comments".
Only to subsequently learn. We can't. Or at least, I can't. Can we?
Has anyone worked out a way to get the keynote tag saying anything more than the default "Value" & "Description" ?
Comment