CSC 225 – Introduction to Software Development CUSTOMER REQUIREMENTS REPORT The project manager has decided to develop the product begun but not completed by an acquired company. (This is the product your team evaluated in the Product Review Report.) The product manager has assigned your development team to develop customer requirements based on customer experience using the product.  Your team needs to gather data on the experience of novices (someone who rarely used this type of product) and experts (someone who frequently uses this type of product.)  Customer experience may be influenced by factors such as age and gender; therefore, demographic data is important for the product manager.  Customers may or may not be able to articulate their experience. Your team needs to gather data directly from customers with a questionnaire, for example, and by observing customers using the product. Your team’s report needs to make recommendations for developing the product to meet customer needs. The project manager has asked your team to make a ten-minute presentation summarizing the report. Your team’s evaluation report and presentation provides the project manager with critical information to plan how to develop the product. YOUR DELIVERABLES 1. The project manager has asked your team to prepare a three-to-five-page requirements report. 2. The project manager has asked your team to present significant findings from the requirements report in a ten-to-fifteen-minute meeting. WHAT YOUR READER WILL DO WITH THE COMMUNICATIONS YOU PROVIDE The manager must develop a plan for completing the project. Therefore, the manager wants your team to answer the following technical questions: 1. How usable is the product for novice and expert users? 2. What factors affect the user’s ability to use the product? 3. What are the most significant factors that affect user’s ability to use the product? You must provide answers to these questions in a manner that helps the manager develop a plan. The manager must evaluate your team to determine whether it is capable of completing the project. The manager will use your team’s report to answer the following questions: 1. Can your team teach novice to expert users how to use the product? 2. Can your team gather useful data on user experience with the product? 3. Can your team identify significant factors that affect user experience? 4. Are you and the other team members able to work together effectively? You need to present your information in a way that persuades the manager that your team is technically proficient and effective at collaborating on a complex project.

1

CSC 225 – Introduction to Software Development LEARNING OBJECTIVES FOR THIS ASSIGNMENT While working on this assignment, focus on developing your ability to perform these technical tasks: 1. Teach novice to expert users how to use the software product. 2. Gather data on user experience including demographic, experience level, and request versus observation. 3. Analyze data to identify strengths and weaknesses of the software product. 4. Create a development plan for the program based on analysis of customer experience. 5. Identify the key technical information about a program that the project manger wants when deciding how to create a development plan to meet customer requirements. Focus also on developing your ability to perform these communication tasks: 1. Write a report that helps managers make practical decisions efficiently. [Writing] 2. Write a report that builds a manager’s confidence in your team’s technical and communication abilities. [Writing] 3. Write a report that persuades mangers to accept your recommendation. [Writing] 4. Select key information from written report useful to the project manager. [Speaking] 5. Create an informative and useful presentation for the project manager. [Speaking] 6. Demonstrate trustworthy technical expertise and communication skills. [Speaking & Teaming] 7. Deliver your presentation in a professional manner that supports achievement of your goals. [Speaking & Teaming] 8. Collaborate effectively on a software development team. [Teaming] 9. Organize and execute a meeting with the project manager and the software development team. [Teaming] 10. Develop knowledge of individual team member skills and trust among team members. [Teaming] ASSIGNMENT SCHEDULE Friday (8/31): Introduction to customer requirements. Wednesday (9/5): Introduction to evaluating user experience. Friday (9/7): Submit your report and make your presentation. Peer review of presentations. GRADING CRITERIA The grading criteria for your team’s written report and presentation are presented in the attached rubrics

2

CSC 225 – Introduction to Software Development Customer Requirements Report

Technical Rubric
TECHNICAL ABILITIES Ability
Teach novice to expert users how to use a software product.

Details
Create a plan to teaching novices

Report Section
Instruction Section

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Plan description with specific steps for a novice Plan description is disorganized, generic, or is not appropriate for a novice Plan description is disorganized, generic, or is not appropriate for a expert Individual user descriptions, no synthesis, changes in a list, or no supporting evidence Useful demographic data missing or not useful data included, missing data, or not listed in a table Data missing or not listed in a table Missing request, corresponding data, sample question, or not in a table

Points

Create a plan for teaching experts

Plan description with specific steps for a expert

Identify changes in each plan from teaching experience

Gather data on user experience.

Gather demographic data for each user

Data Section

Synthesize experience with novices and experts, and list specific changes to each plan support by evidence Useful demographic data for all users listed in a table

Gather experiencelevel data for each user Gather change requests by questioning users

Experience-level data for all users listed in a table Change requests listed in a table with corresponding experience-level and demographic data.

3

CSC 225 – Introduction to Software Development
Include sample questions Gather change requests by observing users Observed requests listed in a table with corresponding experience-level and demographic data List of best product features with a brief and useful description with evidence from gathered data and user experience List of product poorest features with a brief and useful description with evidence from gathered data and user experience Describes accurately the nature and amount of work required to advance each of the program’s weaknesses to a level that would improve users experience Each recommendation is clearly based on issues explicitly described in the analysis section Provides enough detail about each recommendation to enable a manager to incorporate it into a project plan Missing request, corresponding data, , or not in a table

Identify strengths and weaknesses of the software product.

Identify and describe which product features provided the best user experience

Analysis Section

Best product features not in a list, not useful description, or inappropriate or missing evidence Poorest product features not in a list, not useful description, or inappropriate or missing evidence Omits or describes inaccurately the work required to advance each of the program’s weaknesses to a level that would improve users experience Recommendations are not based on issues explicitly described in the analysis section Describes recommendations vaguely so a manager would not be able to incorporate it into a project plan

Identify and describe which product features provided the poorest user experience Create a development plan for the partially completed program. Recommend a development plan based on prioritization of product weakness and change requests Recommen dations Section

4

CSC 225 – Introduction to Software Development Customer Requirements Report

COMMUNICATION RUBRIC
COMMUNICATION ABILITIES Ability
Report helps project manager make practical decisions efficiently

Details
Provides critical information useful to the reader Critical information is easily accessible to the reader

Comm Skill
Writing

EVIDENCE EXAMINED TO EVALUATE YOUR COMMUNICATIONS ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Contains all information useful to the reader and none that is not useful Uses text formatting, organization (e.g., headers), and graphic devices (e.g., lists and tables) that makes information easily accessible to the reader Uses style and tone appropriate for the workplace Useful information is missing or not useful information is included Fails to use formatting, organization, or graphics that makes information accessible to the reader

Points

Report builds project manager’s confidence in team’s technical and communicatio n abilities

Concise and appropriate writing style for project manager Uses precise terms appropriate for the reader

Writing

Uses terms and concepts familiar to the reader, or explains unfamiliar terms or concepts

Uses informal style and tone that is inappropriate for the workplace Misuses terms or concepts or uses terms or concepts unfamiliar to the reader without explanation Key findings are explained inaccurately or imprecisely Fails to used evidence from user training to support key findings

Provides accurate and precise explanations

Key findings are accurately and precisely explained Uses evidence from user training to support key findings

Uses credible evidence to support explanations

5

CSC 225 – Introduction to Software Development

Report persuades project manager to accept your recommendati on

Uses correct and appropriate spelling, grammar, etc. Integrates and interprets findings

Writing

Uses correct spelling, grammar, etc. throughout report Provides a summary that prioritizes and integrates individual findings and synthesizes an interpretation Provides a development plan that recommends actions that are supported by key findings

Several spelling, grammar, etc. errors in report Summary lists without prioritizations or fails to synthesize individual findings

Persuasively describes development plan

Select key information from written report useful to the project manager

Select information the demonstrates key features user training Select information that demonstrates significant features of the user training sample Select information that demonstrates significant factors affecting user experience Select information that recommends plans for program development Key information is presented

Speaking

Concisely and accurately demonstrates key features of user training Concisely and accurately demonstrates significant features of the user training sample

Development plan that is does not recommend actions or is not supported by key findings Selected features are incomplete or redundant Significant features are missing, insignificant features are included, or irrelevant features

Concisely and accurately demonstrates significant factors affecting user experience

Significant factors are missing, insignificant factors are included, or irrelevant factors

Create and informative and useful presentation

Speaking

Concise and accurate recommendations for program development Succinctly presents key information

Significant recommendations missing Omits or inaccurately presents key information

6

CSC 225 – Introduction to Software Development
for the project manager Handouts, visuals, demonstrations, etc. support and complement the presentation Uses concise, accurate, and useful support materials to support and complement the presentation Uses verbose, inaccurate, or extraneous support materials that detract from or confuse the presentation Order does not relate to the order of the written report or does not support report understanding Lacks focus or is disorganized; not useful for the project manager

Report order is clear from the presentation

Orders presentation to support the order and understanding of the written report Speaking and Teaming Demonstrates a clear understanding how to organize a presentation useful to the project manager Demonstrates careful planning, avoids first-time problems, and anticipates potential problems Demonstrates a clearly defined role for each team member Attire for each team member is appropriate for the meeting Demonstrates a clear and accurate understanding of questions, and accurately and respectfully answers each Teaming Each task is independent,

Demonstrate trustworthy technical expertise and communicatio n skills

Focused and organized presentation

Carefully planned and well-executed presentation

Demonstrations lack of preparation and inadequate planning

Each team member’s role is clearly defined

Team member roles are unclear

Each team member is properly attired for the meeting Questions are accurately, authoritatively, and respectfully answered

Team members under dress or over dress for the meeting Demonstrates lack of understanding or the lack of ability to explain answers to questions. Lack of respect for the questioner Tasks are not

Collaborate

Breakdown the

7

CSC 225 – Introduction to Software Development
effectively on a software development team software development project into small, independent task clearly defined, and contributes to the overall software development task independent, are vague or unclear, or do not contribute to the software development task Some team assigned tasks that take too little or too much time, and teams are assigned tasks that fall short of or exceed the allotted time Individuals and small groups are unaware of the state of other individual or small group task Results of each task are not clear or are not easy to access No meeting announcement, missing information, or inadequate advanced notice One or more required attendees absent or late Omitted major topics, time not on task, not enough time to answer all questions

Effectively and equitable assign tasks to individuals or small groups of developers that can be completed in the allotted time

Each team is assigned tasks that can be accomplished in the allotted time and tasks are evenly assigned

Effectively coordinate task among individuals or small groups

Each individual or small group is aware of the state of tasks assigned to other individuals or small groups Results of each tasks are collected in a uniform, easy to use document Meeting announcement is sent with date, time, and place in advance

Organize and execute a meeting with the project manager and the software development team

Effectively and efficiently coordinate results from each task Required attendees are notified of the meeting arrangement

Teaming

Required attendees are present on time

All required attendees present on time

Meeting is wellorganized and executed

All major topics are presented, no time is wasted, all questions are answered in the allotted time

8

CSC 225 – Introduction to Software Development
Develop knowledge of individual team member skills and trust among team members Identify skills of each team member Teaming Team members are able to clearly state at least two strengths and weaknesses for each team member Team members complete assigned tasks and wait for others to complete assigned tasks Team members cannot identify team member strengths or weaknesses

Develop trust among team members

Team members do not complete assigned tasks or do tasks assigned to others

9



Customer Requirements

One Week

Writing, Speaking, Teaming

Requirements

The project manager has decided to develop the product begun but not completed by an acquired company. The product manager has assigned your development team to develop customer requirements based on customer experience using the product. The project manager will use your requirements to advise upper management on the status of the project.

4-6

The course (CSC 225 – Introduction to Software Development) is a sophomore-level, experiential introduction to software development that focuses on learning basic software development principles and communications skills by developing an ongoing project. The course project, Tank Wars, continues from the previous semester and is packaged for the next semester.

Over the course there are five set-up assignments
• Program Review Report
• Customer Requirements Report
• Prioritized Bug/Enhancement Report
• Project Management Tools Report
• Preliminary Test Plan Report
that provide background for four two-week Scrum Cycles included in the Scrum Process Management assignment.

Each assignment is a specific Technical Rubric.

The Communication Skills Rubric is the same for all six assignments. Communication skills are assessed cumulatively from the rubric. Communication skills that are to be assessed in this assignment are in red. Communication skills assessed on in earlier assignments and that will continue to be assess in this assignment are in green. Communication skills not assess are in black. All communication skills are assessed for the Scrum Process Management assignment.

Writing Test Cases

One Week

Writing

Creating testing data to find bugs in code.

CSC 225 – Introduction to Software Development PROGRAM REVIEW REPORT You work for company that has bought out a smaller company that was developing several new products. The project manager has assigned your development team to evaluate one of the projects that was begun but not completed by the acquired company. Your evaluation report will include recommendations for completing the project. The project manager has asked your team to make a tenminute presentation summarizing the report. Your team’s evaluation report and presentation provides the project manager with critical information to plan how to develop the product. YOUR DELIVERABLES 1. The project manager has asked your team to prepare a five-to-seven-page evaluation report. 2. The project manager has asked your team to present significant findings from the evaluation report in a ten-minute meeting. WHAT YOUR READER WILL DO WITH THE COMMUNICATIONS YOU PROVIDE The manager must develop a plan for completing the project. Therefore, the manager wants your team to answer the following technical questions: 1. Does the program run? 2. What does the program do? 3. What is the current state of the program? 4. What is the current state of the project documentation? 5. What needs to be done to complete the project? You must provide answers to these questions in a manner that helps the manager develop a plan. The manager must evaluate your team to determine whether it is capable of completing the project. The manager will use your team’s report to answer the following questions: 1. Can your team correctly install the program? 2. Can your team identify and correct all incomplete and incorrect aspects of the program? 3. Are you and the other team members able to work together effectively? You need to present your information in a way that persuades the manager that your team is technically proficient and effective at collaborating on a complex project. LEARNING OBJECTIVES FOR THIS ASSIGNMENT While working on this assignment, focus on developing your ability to perform these technical tasks: 1. Evaluate installation of existing project software. 2. Analyze operation of the program. 3. Identify, describe, and test (reproduce) bugs. 4. Analyze documentation to determine each document’s purpose, accuracy, and usefulness. 5. Create a development plan for a program based on evaluations of its installation, operation, bugs, and documentation. 6. Identify the key technical information about a program that the project manger wants when deciding how to create a development plan with an incomplete project. 1

CSC 225 – Introduction to Software Development Focus also on developing your ability to perform these communication tasks: 1. Read documentation analytically to evaluate its effectiveness. [Reading] 2. Write a report that helps managers make practical decisions efficiently. [Writing] 3. Write a report that builds a manager’s confidence in your team’s technical and communication abilities. [Writing] 4. Write a report that persuades mangers to accept your recommendation. [Writing] 5. Select key information from written report useful to the project manager. [Speaking] 6. Create an informative and useful presentation for the project manager. [Speaking] 7. Demonstrate trustworthy technical expertise and communication skills. [Speaking & Teaming] 8. Deliver your presentation in a professional manner that supports achievement of your goals. [Speaking & Teaming] 9. Collaborate effectively on a software development team. [Teaming] 10. Organize and execute a meeting with the project manager and the software development team. [Teaming] 11. Develop knowledge of individual team member skills and trust among team members. [Teaming] ASSIGNMENT SCHEDULE Monday (8/27): Introduction to evaluating the installation and operation of a partially completed program. Introduction to team management of program evaluation. Wednesday (8/29): Introduction to evaluating the documentation of a partially completed program. Introduction to effective report writing, presentation, and meeting skills. Friday (8/31): Submit your report and make your presentation. Peer review of presentations. GRADING CRITERIA The grading criteria for your team’s written report and presentation are presented in the attached rubrics

2

CSC 225 – Introduction to Software Development Program Review Report

Technical Rubric
TECHNICAL ABILITIES Ability
Evaluate installation of a partially completed program

Details
Install a program

Report Section
Installation Section

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Describes installation process accurately Focuses on the major steps taken Describes each major problem encountered precisely; summarizes the amount and kinds of minor problems encountered Describe accurately the program’s overall purpose, major parts, and the way the parts work together to achieve the purpose Describes installation process inaccurately Provides a narrative of every step taken Omits major problems encountered or describes them imprecisely; describes in detail each minor problem encountered Omits the description of the program’s overall purpose, describes some or all of its major parts inaccurately, possibly omitting some; fails to tell how the parts work together. Describes features that are unnecessary to understanding the program’s purpose, major parts, operation, and purpose Describes a method

Points

Verify that the installation has worked Identify in technical terms problems with the program’s installation

Determine the intended purpose and operation of a partially completed program

Develop an accurate “mental model” of a program’s major parts, the way the parts operate together, and the overall purpose the program serves

Program Overview Section

Focuses on major features of the program

Evaluate

Develop and use an

Program

Describes an efficient,

3

CSC 225 – Introduction to Software Development
operation of a program efficient, thorough method for evaluating a program’s operation Evaluation Section thorough method used to evaluate the program’s operation Describes precisely each major problem encountered that is inefficient and lacks thoroughness

Omits major problems encountered or describes them imprecisely Describes in detail each minor problem encountered Omits many parts of the program’s documentation. Omits or inaccurately describes the purpose, accuracy and usefulness of some or all documents Omits, states inaccurately, or describes imprecisely the additions, deletions, or modifications needed to make each document sufficiently useful Omits or inaccurately identifies what must be done to make some or all of the documentation sufficiently accurate

Evaluate a program’s documentation

Identify all parts of the program’s documentation Accurately determine each document’s purpose, accuracy, and usefulness Determine what, if anything, must be done to make the documentation sufficiently accurate and useful

Documentation Evaluation Section

Summarizes the amount and kinds of minor problems encountered Identifies all parts of the program’s documentation

Describes accurately the purpose, accuracy, and usefulness of each part

Describes precisely the additions, deletions, or modifications needed to make each document sufficiently useful

Succinctly presents the information in an easy-touse table that enables the reader to quickly find relevant information for each part

4

CSC 225 – Introduction to Software Development
and useful. Presents Inaccurate or incomplete list of documented and undocumented bugs Omits a description of the steps used to test documented bugs, omits steps, and results missing. Omits or describes inaccurately the undocumented bugs Omits and inaccurately describe the factors that must be addressed

Identify, describe, and test all bugs

Develop and use a correct, complete test to repeat each documented bug Identify all undoucmented bugs and explain why they are bugs

Bug Evaluation Section

Lists accurately all documented and undocumented bugs

Describes fully steps used to test bug and test results for all documented bugs

Describes the behavior of undocumented bugs Synthesize evaluations of the various components of a program Identify and describes the critical factors that must be addressed in preparing a plan for completing the program Determine how far each factor is from an acceptable state Discussion Section Identifies and accurately describes all of the critical factors that must be addressed

Accurately describes how close each factor is to an acceptable state

Fails to describe how close each factor is to an acceptable state or conveys inaccurate judgments Fails to present an overall portrait of the scope and nature of the work required or presents mistaken judgments do not provides a reliable basis for formulating a plan for completing the program

Synthesize these general judgments into an overall evaluation of the scope and nature of the work that can form the basis of a plan for completing the program

Characterizes the overall scope and nature of the work required in a way that provides a reliable basis for formulating a plan for completing the program

5

CSC 225 – Introduction to Software Development
Create a development plan for a partially completed program Recommend a development plan based on a synthesis and prioritization of problems they discovered in their evaluation Recommen dations section Describes accurately the nature and amount of work required to advance each of the program’s critical factors to a level that would enable to program to perform acceptably Omits or describes inaccurately the work required to advance each of the program’s critical factors to a level that would enable to program to perform acceptably

Each recommendation is clearly based on issues explicitly described in the evaluation and discussion sections Provides enough detail about each recommendation to enable a manager to incorporate it into a project plan

Recommendations are not based on issues explicitly described in the evaluation and discussion sections Describes recommendations vaguely so a manager would not be able to incorporate it into a project plan

6

CSC 225 – Introduction to Software Development Program Review Report

COMMUNICATION RUBRIC
COMMUNICATION ABILITIES Ability
Report helps project manager make practical decisions efficiently.

Details
Provides critical information useful to the reader

Comm Skill
Writing

EVIDENCE EXAMINED TO EVALUATE YOUR COMMUNICATIONS ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Contains all information useful to the reader and none that is not useful Useful information is missing or not useful information is included Fails to use formatting, organization, or graphics that makes information accessible to the reader

Points

Critical information is easily accessible to the reader

Uses text formatting, organization (e.g., headers), and graphic devices (e.g., lists and tables) that makes information easily accessible to the reader Uses style and tone appropriate for the workplace Writing Uses terms and concepts familiar to the reader, or explains unfamiliar terms or concepts

Concise and appropriate writing style for project manager Report builds project manager’s confidence in team’s technical and communicatio n abilities. Uses precise terms appropriate for the reader

Uses informal style and tone that is inappropriate for the workplace Misuses terms or concepts or uses terms or concepts unfamiliar to the reader without explanation Key findings are explained inaccurately or imprecisely Fails to used evidence from program review

Provides accurate and precise explanations

Key findings are accurately and precisely explained Uses evidence from program review to

Uses credible evidence to support explanations

7

CSC 225 – Introduction to Software Development
support key findings Uses correct and appropriate spelling, grammar, etc. Integrates and interprets findings Uses correct spelling, grammar, etc. throughout report Provides a summary that prioritizes and integrates individual findings and synthesizes an interpretation Provides a development plan that recommends actions that are supported by key findings Speaking Concisely and accurately demonstrates key features of the program operation Concisely and accurately demonstrates significant problems that define the current state of the project Concisely and accurately demonstrates significant bugs that define the current state of the project Concisely and accurately synthesizes the current state of the project Concise and accurate to support key findings Several spelling, grammar, etc. errors in report Summary lists without prioritizations or fails to synthesize individual findings

Report persuades project manager to accept your recommendati on.

Writing

Persuasively describes development plan

Select key information from written report useful to the project manager

Select information the demonstrates key features of program operation Select information that demonstrates significant problems encountered

Development plan that is does not recommend actions or is not supported by key findings Selected features are incomplete or redundant

Significant problems are missing, insignificant problems are included, or irrelevant problems Significant bugs are missing, insignificant bugs are included, or irrelevant bugs

Select information that demonstrates significant bugs

Select information that synthesizes the current project state Select information that

Significant factors missing from the synthesis Significant

8

CSC 225 – Introduction to Software Development
recommends plans for program development Key information is presented recommendations for program development Succinctly presents key information recommendations missing Omits or inaccurately presents key information Uses verbose, inaccurate, or extraneous support materials that detract from or confuse the presentation Order does not relate to the order of the written report or does not support report understanding Lacks focus or is disorganized; not useful for the project manager

Create and informative and useful presentation for the project manager

Speaking

Handouts, visuals, demonstrations, etc. support and complement the presentation

Uses concise, accurate, and useful support materials to support and complement the presentation

Report order is clear from the presentation

Orders presentation to support the order and understanding of the written report Speaking and Teaming Demonstrates a clear understanding how to organize a presentation useful to the project manager Demonstrates careful planning, avoids first-time problems, and anticipates potential problems Demonstrates a clearly defined role for each team member Attire for each team member is appropriate for the meeting Demonstrates a clear and

Demonstrate trustworthy technical expertise and communicatio n skills

Focused and organized presentation

Carefully planned and well-executed presentation

Demonstrations lack of preparation and inadequate planning

Each team member’s role is clearly defined

Team member roles are unclear

Each team member is properly attired for the meeting Questions are

Team members under dress or over dress for the meeting Demonstrates lack of

9

CSC 225 – Introduction to Software Development
accurately, authoritatively, and respectfully answered accurate understanding of questions, and accurately and respectfully answers each Teaming Each task is independent, clearly defined, and contributes to the overall software development task understanding or the lack of ability to explain answers to questions. Lack of respect for the questioner Tasks are not independent, are vague or unclear, or do not contribute to the software development task Some team assigned tasks that take too little or too much time, and teams are assigned tasks that fall short of or exceed the allotted time Individuals and small groups are unaware of the state of other individual or small group task Results of each task are not clear or are not easy to access No meeting announcement, missing information, or inadequate advanced notice One or more required attendees absent or late

Collaborate effectively on a software development team

Breakdown the software development project into small, independent task

Effectively and equitable assign tasks to individuals or small groups of developers that can be completed in the allotted time

Each team is assigned tasks that can be accomplished in the allotted time and tasks are evenly assigned

Effectively coordinate task among individuals or small groups

Each individual or small group is aware of the state of tasks assigned to other individuals or small groups Results of each tasks are collected in a uniform, easy to use document Meeting announcement is sent with date, time, and place in advance

Organize and execute a meeting with the project manager and the software development team

Effectively and efficiently coordinate results from each task Required attendees are notified of the meeting arrangement

Teaming

Required attendees are present on time

All required attendees present on time

10

CSC 225 – Introduction to Software Development

Meeting is wellorganized and executed

Develop knowledge of individual team member skills and trust among team members

Identify skills of each team member

Teaming

All major topics are presented, no time is wasted, all questions are answered in the allotted time Team members are able to clearly state at least two strengths and weaknesses for each team member Team members complete assigned tasks and wait for others to complete assigned tasks

Omitted major topics, time not on task, not enough time to answer all questions Team members cannot identify team member strengths or weaknesses

Develop trust among team members

Team members do not complete assigned tasks or do tasks assigned to others

11



Program Review

One Week

Writing, Speaking, Teaming

Install and deploy

You work for company that has bought out a smaller company that was developing several new products. The project manager has assigned your development team to evaluate one of the projects that was begun but not completed by the acquired company. Your evaluation report will include recommendations for completing the project. The project manager will use your recommendations to advise upper management whether to develop the project.

4-6

The course (CSC 225 – Introduction to Software Development) is a sophomore-level, experiential introduction to software development that focuses on learning basic software development principles and communications skills by developing an ongoing project. The course project, Tank Wars, continues from the previous semester and is packaged for the next semester.

Over the course there are five set-up assignments
• Program Review Report
• Customer Requirements Report
• Prioritized Bug/Enhancement Report
• Project Management Tools Report
• Preliminary Test Plan Report
that provide background for four two-week Scrum Cycles included in the Scrum Process Management assignment.

Each assignment is a specific Technical Rubric.

The Communication Skills Rubric is the same for all six assignments. Communication skills are assessed cumulatively from the rubric. Communication skills that are to be assessed in this assignment are in red. Communication skills assessed on in earlier assignments and that will continue to be assess in this assignment are in green. Communication skills not assess are in black. All communication skills are assessed for the Scrum Process Management assignment.

design document, code, comments, pseudo-code, test results, documentation, listening to presentations, oral presentations, reflection, team meetings, tech report

Several Weeks

Reading, Writing, Speaking, Teaming

Design, linear data structures, research, problem solving

TEAM DESIGN DOCUMENT
Technical Task: Most real-world software development projects involve working as a team.
Professional Setting: Students work for a software company.
Professional Role: Students are members
Deliverable: Design document.
Real-world Audience: A project manager.
How the Audience will USE the students' communication: The project manager will use the students' design document to do the following: (1) Develop a plan for completing the project, and (2) Determine whether the team is capable of completing the project.
Additional Notes: Whether it is working with other developers, business people, managers, customers, or users, you must be able to adapt to different personalities and deliver a working product that meets the customer’s requirements.


ADDITIONAL SCENARIO:
In addition, as a software developer in the work force, you may have to do some research to find a solution to a problem. In this assignment, you will be given a sub-task (handling of the probability of an airplane arriving or taking off) for which there is not a solution in your textbook. For example, this will require you to read other resources (such as the internet) to understand how to do random number generation.

4-6

Memo

Less than a week

Writing
Reading

Research
Project management

Many software development projects are delivered late, or fail all together, due to mismanagement. One aspect of effective management is to make realistic estimates of the effort (or time) needed to create a software product. Another aspect is effective team management. This reading presents some rules of thumb from a leader in the software engineering community. In this memo to your supervisor, you will identify what you consider to be the most important point in helping to reduce risks in the development process.

In an internship or in your career you will likely be called upon to estimate the effort required for a project. This knowledge will give you a head-start in your internship or job situation.

N/A