Professional Documents
Culture Documents
Who We Are
An experiential learning program that provides technology solutions for our partners, and realworld experience for our students Housed within the College of Business at Oregon State University Two components: Hardware & software product testing Custom software application development Made up of 6 full-time staff and between 40 and 50 Student Interns
Where We Began
Curriculum Workflow, Our First .NET Application
No Defined Process Two Developers Just Getting it Done Valued Client Interaction and Feedback
Where We Began
Discover Requirements Via User Feedback
Testing
Result: users perception of the system skewed since they tested it, and quality issues.
Defect Tracking
Result: bugs slip through the cracks after they had been identified, and quality issues.
Task Tracking
Result: unable to manage large numbers of developers and keep them on task. Result: no metrics upon completion on the effort put into the project, which leads to an inability to make better estimates of future projects.
Task Tracking
Advantage: focus on the project without being distracted by other projects allowing tasks to be completed without much tracking.
What is TFS?
Connects developers, testers, managers, Work creating a global, Version analysts by Item Tracking Control collaborative environment for the entire team.
Reporting Build Automation Team Communications
Process Templates
MSF Agile
Relies on team member responsibility Focuses more on the project Less rigid
Review of Agile
As stated at www.agilemanifesto.org:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Work Items
Work Streams
A Group of Activities (can include work items) Can Cross Multiple Roles
Where We Will Be
Documentation & Code Standards
Defined scenarios for capturing requirements and static code analysis and reviews will help improve communication and code maintainability.
Testing
Integrating testing from the beginning at the unit and system levels will help create quality code.
Defect Tracking
Bug work items will help keep bugs from slipping through the cracks improving the quality of the applications.
Task Tracking
Task work items will help communicate to the team what needs to be done and allow project managers to track progress and keep the customer informed.