[p4] Perforce and Scrum

steve at vance.com steve at vance.com
Mon Nov 17 14:36:25 PST 2008

You'll tend to create fewer branches and when you do they'll generally be
per Scrum team per iteration. If you're really scaling it up, you may have
some integration branches in there for teams working in common areas.
Generally, you won't need to do that if your TDD is in place and you're
doing it properly.


Original Message:
From: Todd Zarnes todd.zarnes at activant.com
Date: 	Mon, 17 Nov 2008 15:19:57 -0600
To: perforce-user at perforce.com
Subject: [p4] Perforce and Scrum

We have historically been a waterfall development shop but are trying
our hands at more Agile and Scrum approaches.  Anybody do anything
different with your Perforce depots to support a Scrum approach?

ToddZarnes | Activant Eclipse | SCM Manager
Notice: This transmission is for the sole use of the intended recipient(s)
and may contain information that is confidential and/or privileged.  If you
are not the intended recipient, please delete this transmission and any
attachments and notify the sender by return email immediately.  Any
unauthorized review, use, disclosure or distribution is prohibited.
perforce-user mailing list  -  perforce-user at perforce.com

mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http://link.mail2web.com/Personal/EnhancedEmail

More information about the perforce-user mailing list