220 likes | 331 Views
A .NET-based Project Management Tool for Senior Projects at Stanford. Robert P. Plummer Department of Computer Science Stanford University plummer@cs.stanford.edu. CS194 – Software Project. One quarter duration (10 weeks) Team size: 1 to 4 Topics chosen by students.
E N D
A .NET-based Project Management Tool for Senior Projects at Stanford Robert P. Plummer Department of Computer Science Stanford University plummer@cs.stanford.edu
CS194 – Software Project • One quarter duration (10 weeks) • Team size: 1 to 4 • Topics chosen by students
CS194 – Software Project • 3 or 4 weeks of lectures on software engineering • Weekly team meetings after that • Software Faire at the end of the quarter
CS194 – Software Project CS194 satisfies the "writing in the major" requirement Documents produced: • Mini-proposal (email) • Formal proposal • Software specification • Design document • Personal responsibilities document
CS194 – Software Project Software Faire http://forum.stanford.edu/events/cs194-software-faire.html
Critical Success Factors for • Senior Project • Good software engineering • Enthusiasm • Focus • Harmony • Smarts
Why do some teams have problems? • Overambitious project • Inadequate definition of product • Failure to record decisions made • Bug list on the back of an envelope
Why do some teams have problems? • Overambitious project • Inadequate definition of product • Failure to record decisions made • Bug list on the back of an envelope • Poor group communication
CodeSavvy: A Project Management Tool • Source code management • Bug tracking • Group communication
CodeSavvy: A Project Management Tool • Source code management • Bug tracking • Group communication • Document repository • Milestone tracking • Design tools
CodeSavvy: Source code management • Based on CVS • Our own UI • Files stored in student's disk space • Version control, etc.
CodeSavvy: Bug tracking • A way to record and track defects • Usual attributes: severity, status, etc. • A discussion for each bug
CodeSavvy: Group communication • Our metaphor: conversations
CodeSavvy: Group communication • Our metaphor: conversations • Blur the distinction between instant messaging and email • -- Real-time for team members online • -- Stored for those who are not online
CodeSavvy: Technology • A Windows application • Coded in C#
CodeSavvy: Challenges • Users have little tolerance for problems with communications tools • We are asking for cultural changes • It won’t help if they don’t use it!
CodeSavvy: A Research Vehicle • We will log events (but not content) • We will try to find out how our teams work -- Message flow -- Bug flow -- Group interactions
CodeSavvy: The Future • Release to CS194: winter 2003 • Release to outside world: spring 2003?? • Let me know if you are interested!
CodeSavvy: The Team • Dan Skarbek • Audrey Tsang • Beau Baudier • Hoop Somuah • Charles Srisuwananukorn • Ramesh Balakrishnan Thanks to Mark Hayes and Dan Fay of Microsoft for help and support Robert P. Plummer Department of Computer Science Stanford University plummer@cs.stanford.edu