4 ms·
Having followed the process as described, i'd agree. If a project runs for more than a few months, you forget why decisions were made. I don't think XP in gener
by twic 7y ago
Having followed the process as described, i'd agree. If a project runs for more than a few months, you forget why decisions were made. I don't think XP in general has a great story about how to deal with this.
- technion 7y agoI'd be less worried about "forgetting" and forever worried about a manager just saying "you obviously forgot (something I just decided)". I mean it happens even when there's documentation I can pull up and say "well actually..", I'd hate to imagine otherwise.
- JustSomeNobody 7y agoI love email for this. That way I can always pull up the email and say, "this is what we decided." I follow up all meetings with email(s).
- jacques_chester 7y agoYes, this is one of my pet peeves. Pivotal R&D has struggled with maintaining context. For multi-megaSLOC codebases with many moving parts, organic memory begins to fall a bit short. Different teams deal with this differently. Some write design notes, some keep architecture design records. But IMO it's one of our weaknesses.