Cubicles  
Software Process Management  
line decor
  HOME  ::  
line decor
   
 
Tasks
large product photo   Novice Coder

Mythical Man Month Article Summaries:

Write a paper explaining the topic of an article from The Mythical Man Month by Brooks (1 - 3 pages). The paper must contain:

  • Article Synopsis
  • Description of applicability to current software development practice.
  • How you think the ideas can be appied.
  • Areas you agree and areas you disagree along with explanations and support.

Mythical Man Month Article Presentations:

For an article from The Mythical Man Month, do a presentation in front of the class covering:

  • Article summary
  • Areas of the article and how they specifically apply to software development.
  • Modern practices and how the article differs in these areas.

Your presentation must incorporate visual support. This can also be done as a team effort. All team members must participate. Presentations will be scheduled with the instructor.

large product photo  

Agile Development Chapter Summaries:

For a chapter in the Agile Development, write a 1-3 page paper. The paper must contain:

  • Chapter Synopsis
  • Description of applicability to current software development practice.
  • How you think the ideas can be appied.
  • Areas you agree and areas you disagree along with explanations and support.

Agile Development Chapter Presentations:

For a chapter from Agile Development, do a presentation in front of the class covering:

  • Chapter summary
  • Areas of the chapter and how they specifically apply to your ideas of software development.
  • How the chapter will be applied in your software development practice..

Your presentation must incorporate visual support. This can also be done as a team effort. All team members must participate. Presentations will be scheduled with the instructor.

large product photo  

Initial Project Requirements List:

First develop a sequence of user stories related to the project you will be working on for the year. User stories are a descriptive narrative of an instance of use of your system.

From your user stories, develop a requirements list detailing functional and non functional requirements.. The functional requirements list will have single statement engineering requirements decomposed into functional ares. Non functional requirements will be split into groups based on area of system application. This artifact, in it's final form, must be produced with a word processor.

Requirements evaluation will be based on:

  • Document Structure
  • Requirements Analysis
  • Functional Requirements
  • Requirements Organization
  • Non-functional Analysis
  • Prioritization

User story evaluation will be based on:

  • Document Structure
  • System Coverage
  • Story Coherence
  • Requirements Mapping

Bi-Weekly Status Reports:

Once your team has acquired a project to work on for the year, you will produce bi-weekly status reports. Each status report must contain:

  • Tasks performed during the previous week.
  • Problems encountered..
  • Proposed problem solutions.
  • Tasks scheduled for the next week along with responsible parties.

Anything else you would like to do.......just ask!