Our teams currently use a combination of a bulletin board and an Excel spreadsheet to track tasks and draw a burning schedule. Pending applications are stored in envelope cards.
This works well when stakeholders are in one place. However, we will soon have Scrum teams in two geographically distant locations, and I'm looking for best practices on how we can use Sharepoint to help us communicate around Scrum artifacts (lag, burn chart, speed, etc. )
How did you use Sharepoint for this purpose, what are the best methods and possible traps?
If you already have SharePoint in your home, as well as a user base that is convenient with it, I think it would be pretty easy to start using it for SCRUM. I would start with the following:
A collection of sites to host 1 site for each project
The scrum site must contain:
Document library for electronic files (add columns for appropriate categorization)
Team members list
Bulletin board
A site can be created from a Wiki site template, if necessary.
Once you get the scrum "feel right" site, save it as a template so that it can be easily deployed.
SCRUM n- , , . , , , .
my $0.02
JT
Sharepoint Agile- , / ., , , . infopath, . infopath : , , , , , .- : , , .. , , .
SEND-RECV-ASSERT, , XML . - Green/Red , .XML, XML. ( ActiveX javascript)( XML- html-). , -, , / ! !:)
- Trello, VersionOne, Rally Basecamp. , , . SharePoint , . Team System , - Team System Wiki . SharePoint , .
SharePoint - , . YMMV.
. , , , - .
SharePoint, , , , . , .
SharePoint , , , . ( , ), , , , , - .
, . , 37signals ( basecamp) - , .
21Scrum - scrum, SharePoint, , ( , ) .
, , SharePoint - , .
SharePoint Release/Sprint, Backlog Back Sprint.
SharePoint - - . http://www.youtube.com/watch?v=XW89M0C3N7Q
.
!
AFAIK, Sharepoint - ASP.net . , ., , .. . , , - , .
. Big Visible. digicam / ( Google ) . , " " . ( ) .
( : 0 sharepoint.. , 2 , )