1 / 22

A .NET-based Project Management Tool for Senior Projects at Stanford

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.

Download Presentation

A .NET-based Project Management Tool for Senior Projects at Stanford

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A .NET-based Project Management Tool for Senior Projects at Stanford Robert P. Plummer Department of Computer Science Stanford University plummer@cs.stanford.edu

  2. CS194 – Software Project • One quarter duration (10 weeks) • Team size: 1 to 4 • Topics chosen by students

  3. 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

  4. 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

  5. CS194 – Software Project Software Faire http://forum.stanford.edu/events/cs194-software-faire.html

  6. Critical Success Factors for • Senior Project • Good software engineering • Enthusiasm • Focus • Harmony • Smarts

  7. 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

  8. 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

  9. CodeSavvy: A Project Management Tool

  10. CodeSavvy: A Project Management Tool • Source code management • Bug tracking • Group communication

  11. CodeSavvy: A Project Management Tool • Source code management • Bug tracking • Group communication • Document repository • Milestone tracking • Design tools

  12. CodeSavvy: Source code management • Based on CVS • Our own UI • Files stored in student's disk space • Version control, etc.

  13. CodeSavvy: Bug tracking • A way to record and track defects • Usual attributes: severity, status, etc. • A discussion for each bug

  14. CodeSavvy: Group communication • Our metaphor: conversations

  15. 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

  16. CodeSavvy: Technology • A Windows application • Coded in C#

  17. CodeSavvy

  18. 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!

  19. 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

  20. CodeSavvy: The Future • Release to CS194: winter 2003 • Release to outside world: spring 2003?? • Let me know if you are interested!

  21. 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

More Related