|
Re: Practice: Slack: msg#00068programming.extreme-programming.xp-explained2
Hi Keith, > How do you prevent "minor tasks that can be dropped if you get > behind" from being interpreted as broken > promises/comittements? One possibility is not to promise them or commit to them. That isn't a foolproof way to prevent people interpreting the change in scope as a broken commitment, but you can sometimes negotiate expectations up front. "We promise to deliver these three things. And if we have time, we'll do those other two things, but we can't promise that until we see how these first three things go." Dale -- Dale Emery, Consultant Inspiring Leadership for Software People Web: http://www.dhemery.com Weblog: http://www.dhemery.com/cwd Positive, adj. Mistaken at the top of one's voice. --Ambrose Bierce ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Practice: Slack: 00068, Tim King |
|---|---|
| Next by Date: | Re: Practice: Slack: 00068, Ron Jeffries |
| Previous by Thread: | Re: Practice: Slacki: 00068, Keith Ray |
| Next by Thread: | Re: Practice: Slack: 00068, Ron Jeffries |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |