design document, code, comments, pseudo-code, test results, documentation, reflection, tech report

Two Weeks

reading, writing, listening

implementation, tools. design, recursion, trees, problem solving, searching, sorting

RESEARCH
Technical Task: In order to learn technical material, one must be able to decipher key concepts through reading.
Professional Setting: Student works for a software company.
Professional Role: Student works along on a task for a project.
Deliverable: Design decisions discussed in design document.
Real-world Audience: Team Lead.
How the Audience will USE the students' communication: The Team Lead will use the student's design decision(s) to determine the feasibility of their proposed solution.
Additional Notes: Of course, the reading of technical material is not like reading a novel, and one must be able to transfer the pertinent information to a useful form. The two methods of communicating design to others are: speaking and writing. In order for others to digest your intentions, one must learn to effectively write their ideas so that it can be interpreted at the reader’s discretion – either due to remoteness or time.

N/A

CSC 225 – Introduction to Software Development SCRUM PROCESS MANAGEMENT Your project manager has received approval to develop the product that was started by not completed by an acquired company. From your past work, he has developed confidence in your team’s ability to successfully develop the product. Based on your recommendation, your project manager has decided to use Scrum Process Management to manage the project. To successfully manage the project, your team needs to do the following.  Create a work plan from the backlog (prioritized bug/enhancement list) that can be completed in one two-week scrum cycle.  Frequently give progress updates in short scrum meetings.  Demonstrate a working version of the product at the end of each scrum cycle.  Submit a work plan with work completed and resources consumed, and work not completed with an explanation.  Submit individual and team post-mortem reports. Your project manager has asked that you create effective reports and make effective presentations that he can use to keep upper management and the customer informed of progress on the project. YOUR DELIVERABLES 1. The project manager has asked your team to prepare a work plan to manage the product development process. 2. The project manager has asked your team to update the work plan at frequent ten-minute scrum meetings. 3. The project manager has asked your team to demonstrate a working version of the product at the end of each scrum cycle. 4. The project manager has asked your team to report work completed and not completed with resources used for each. 5. The project manager has asked your team to submit a post-mortem report at the end of each scrum cycle. WHAT YOUR READER WILL DO WITH THE COMMUNICATIONS YOU PROVIDE The project manager must keep upper management and the customer informed of the progress of product development. Therefore, the manager wants your team to answer the following technical questions: At the start of a scrum cycle 1. What bugs or enhancements will be included in the next product release? 2. Who will work on each bug fix or enhancement implementation? 3. What resources will be required to complete the bug fix or enhancement implementation? 4. How will successful bug fixes or enhancement implementations be demonstrated? During a scrum cycle 5. What progress has been made on product development? 6. What obstacles have been encountered? 1

CSC 225 – Introduction to Software Development

At the end of a scrum cycle 7. What bugs have been fixed or enhancements implemented? 8. What bugs have not been fixed or enhancements not implemented? 9. What resources were consumed? 10. How can the product development process be improved? You must provide answers to these questions in a manner that helps the manager keep upper management and the customer informed. The manager must evaluate your team to determine whether it is successfully completing the project. The manager will use your team’s reports to answer the following questions: 1. Can your team competently plan a scrum cycle? 2. Can your team frequently make and report progress toward completing the plan? 3. Can your team reflectively analyze the team’s process and recommend improvements? 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. LEARNING OBJECTIVES FOR THIS ASSIGNMENT While working on this assignment, focus on developing your ability to perform these technical tasks: 1. Create a work plan for a scrum cycle. 2. Breakdown backlog items (bugs and enhancements) into work units. 3. Assign work units to team members. 4. Estimate time needed to complete a work unit. 5. Create short-term work unit objectives. 6. Analyze work performed on work units. 7. Maintain (update and adjust) work plan during a scrum cycle. 8. Demonstrate completed work units (bug fixes and enhancements). 9. Analyze individual and team performance. 10. Identify the key technical information about product development that the project manger wants when reporting to upper management and the customer. 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] 2

CSC 225 – Introduction to Software Development 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 Scrum Cycles: 1 – Mon, Oct 1 to Fri, Oct 12 2 – Mon, Oct 15 to Fri, Oct 26 3 – Mon, Oct 29 to Fri, Nov 9 4 – Mon, Nov 12 to Fri, Nov 30

First Monday :

Select Scrum Master for this cycle. Select backlog items from Prioritized Bug/Enhancement Lit for this cycle. Define work units for each backlog item. Assign work units to team members. Estimate time for each work unit. Organize work plan in easy to read and easy to update format. Team ID Cycle Number Start & Stop Dates Backlog Item(s) Work Units Team Member(s) Time Estimate Preliminary Test Plan 10 minute Scrum Meeting (Stand Up) Run by Scrum Master Each team member reports on progress on assigned work unit. What did you do since the last scrum meeting? What obstacles are you encountering? What do you plan to accomplish by the next scrum meeting? 15 minute demo of product What work units were completed? What work units were not completed? Brief explanation for each work unit not completed. Submit completed Work Plan Report with individual time logs. Update backlog (Prioritized Bug/Enhancement List). Team Post Mortem on scrum cycle. Individual Post Mortems on scrum cycle.

First Friday and Second Monday:

Second Friday:

Third Monday:

3

CSC 225 – Introduction to Software Development ROLES AND RESPONSIBILITIES Scrum Master Run scrum meetings Create and update work plan Work unit assignment Work unit time estimates (from team member(s) assigned work unit) Update backlog Complete and submit completed work plan Work units completed/not completed Team members’ time and time logs Team Post Mortem Report Team Members Select backlog items (with Scrum Master) Define work units for backlog items Estimate time for each work unit Develop test plan for each work unit Report at each scrum meeting Maintain time log (date worked, time worked, work unit or task) Demo completed work unit Explain not-completed work unit Individual Post Mortem Submit completed time log to Scrum Master

GRADING CRITERIA The grading criteria for your team’s written report and presentation are presented in the attached rubrics

4

CSC 225 – Introduction to Software Development Scrum Process Management

Technical Rubric
TECHNICAL ABILITIES Ability
Create a work plan

Details
Select backlog items to be completed in scrum cycle.

Report Phase
Before Scrum Cycle

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Lists top priority backlog items that can be completed in on cycle. Omits top priority backlog items, or lists too few or too many items. Work units are not independent or do not complete backlog item.

Points

Break backlog items (bugs and enhancements) into work units. Assign work units to team members.

Work units are independent and together complete a backlog item. Work units are assigned to all team members. Assigned work units can be completed in one cycle. Lists a time estimate for each work unit. Time estimate can be persuasively defended. Verifies successful bug fix or enhancement implementation.

Some team members do not have assigned work units, or have too little or too much for on cycle. Omits time estimates for work units. Time estimate cannot be persuasively defended. Omits critical components of successful bug fix or enhancement implementation. Omits work units to be completed over time period. Objectives

Estimate time needed to complete a work unit.

Create a test plan for each backlog item

Manage product development

Create short-term work unit objectives.

During Scrum Cycle

Lists work units to be complete over a time period. Objective can be

5

CSC 225 – Introduction to Software Development
progress persuasively defended. cannot be persuasively defended. Fails to report progress toward work unit objectives. Cannot identify obstacles impeding progress. Omits progress on work units or fails to identify obstacles on work unit objectives that have fallen behind.

Analyze work performed on work units.

Reports work completed on work unit objectives. Identifies obstacles that impede progress.

Maintain (update and adjusts) work plan during a scrum cycle.

Complete product development cycle

Demonstrate completed work units (bug fixes and enhancements). Explain work units not completed.

End of scrum cycle

Lists work units with amount of progress completed toward completion and identified obstacles on work unit objectives that have fallen behind. Team member(s) demonstrate completed, assigned work units.

Team member(s) fail to demonstrated completed assigned work units. Team member(s) fail to persuasively explain not-completed, assigned work units.

Team member(s) persuasively explain notcompleted, assigned work units. List all completed and not-completed work units with times auditable to individual time logs.

Submit completed Work Plan Report with individual time logs.

Omits completed or not-completed work units or times are not auditable to individual time logs. Completed items not removed, notcompleted items not added, new items not added, or list not

Update backlog.

Complete items removed from Prioritized Bug/Enhancement List and not-completed items and new items added and

6

CSC 225 – Introduction to Software Development
prioritized. Identifies key areas of individual performance that worked well and areas that did not work well. Proposes effective ways to improve individual performance. Identifies key areas of team performance that worked well and areas that did not work well. Proposes effective ways to improve team performance. prioritized. Omits key areas of individual performance that work well or did not work well. Fails to propose effective ways to improve individual performance. Omits key areas of team performance that work well or did not work well. Fails to propose effective ways to improve team performance.

Evaluate product development process

Analyze individual performance.

End of scrum cycle

Analyze team performance.

7

CSC 225 – Introduction to Software Development Scrum Process Management

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

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 Writing

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 to

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

Provides accurate and precise explanations

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

Uses credible evidence to support explanations

8

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

9

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 understanding or the

10

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

11

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

12



Project Plan, Code, Test Results, Demonstration

Several Weeks

Writing, Speaking, Teaming

Project Managment

Your project manager has received approval to develop the product that was started by not completed by an acquired company. From your past work, he has developed confidence in your team’s ability to successfully develop the product. Based on your recommendation, your project manager has decided to use Scrum Process Management to manage the project. The project manager will use your work plan and progress reports 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.

Design diagram

Less than a week

Writing

Design

The purpose of this assignment is to introduce another modeling tool called the System Sequence Diagram (SSD). SSDs are a special case of UML sequence diagrams that illustrate the input and output events between actors and the system. Typically a SSD corresponds to one scenario from a Use Case. The SSD shows the interaction of the actor with the new system, so it is a bridge between conceptual design (analysis) and software design. In this assignment you will sketch a domain model, illustrating the real-world objects for one of your project use cases. Your supervisor will review the domain model and offer comments to help you to refine your understanding of the use case.

N/A

Test Specification

One Week

Writing

Testing

You have been assigned the task of testing a specific piece of software by your team manager. As part of this task you are required to write a test specification that documents the expected behaviors for the different methods of the component or class.

Audience: The audience of your test specification is other testers and developers.

Setting: Software development team.

Deliverables: Test specification and test execution summary.

N/A

coding,
reading design description,
experimental design,
gathering experimental data,
charting,
interpreting data,
writing a report

Two Weeks

reading, writing

linear data structures,
program design,
object oriented language features,
standard library integration,
big-oh analysis

When analyzing a piece of text, it is sometimes useful to count the number of times each word appears and to identify the words that occur most often. One might, for example, process Twitter traffic or text messages among a specific group of people and, after filtering out words that are common in all English text (a, an, the, ...), figure out what the primary subject of the conversation is. In the workplace a developer may be asked to explore a variety of implementations of a frequently used system utility and write a report describing the advantages and disadvantages of each, with emphasis on efficiency.

This assignment can be used even if the students are not familiar with binary search tree implementations, as long as they can figure out how to use the TreeMap API.

The assignment can be adapted to C++, which also has a map class in the STL.

code, runtime-analysis, short-answer prose

Two Weeks

reading, writing

Implementation, hash tables, complexity analysis, linear data structures

Workplace Scenario
You have been hired by a major Casino chain to verify the Bayer-Diaconis theorem, which purports to prove how many times a 52-card playing deck must be riffle-shuffled in order to completely randomize it (that is, make sure that, when done, each card could be anywhere in the deck with equal probability – regardless of where it started.). It is extremely important to the Casino that, before each deal at the Black Jack table, a deck be shuffled enough to make the order random. Failure to do so could lead to potential biases that a player might exploit. But Bayer-Diaconis is an analytic proof – a logical deduction from first principles. Your employer wants empirical evidence that Bayer-Diaconis is correct. One possibility is to have you shuffle the desk for a few billion years and track where the cards end up, but that is impractical. What is practical is to run a simulation and apply a basic statistical tool to establish the actual bound.

Importance: Using simulation to study the behavior of complex systems is one of the primary functions of Computer Science, and this project will expose you to some of the basic principles of the area. At a lower level, it will also require you to work with linked lists – arguably one of the two most important data structures we use.

You will also be asked to read investigate the linked-list data structure and discuss aspects of the reading. In reality, you will often need to pick a data structure appropriate to your problem, frequently choosing between established structures you are unfamiliar with. This will involve a certain degree of research: reading and understanding papers or text on the options, and possibly defending your decision to a colleague, boss, or client. The questions in this assignment are intended both to test your understanding and to make sure you can coherently explain what you have learned to another party.

N/A

design document, code, comments, pseudo-code, test results, documentation, individual presentations, oral presentations, reflection, tech report, video

Two Weeks

reading, writing, speaking

implementation, tools, design, linear data structures, program design, comments, documentation, problem solving

DESIGN PRESENTATION
Technical Task: When presented with a problem in the real-world, the customer is not going to tell you what algorithm or data structure(s) to use. All they know is the problem. It is your job to decide what is the best way to solve the problem, given all the parameters of the domain.
Professional Setting: Student works for a software company.
Professional Role: Software engineer.
Deliverable: Design document.
Real-world Audience: Team Lead and peers.
How the Audience will USE the students' communication: The Team Lead and peers will use the student's design decisions to do the following: (1) suggest other design choices, and (2) determine the feasibility of the project.


ADDITIONAL SCENARIO:
If you cannot present your ideas to management, you will lose their confidence in your abilities. If you cannot effectively present your product and ideas to a customer, you will probably lose their business.

N/A

Design diagram

Less than a week

Writing

Design

The purpose of this assignment is to introduce an object-oriented analysis tool called the domain model. The domain model is a visual representation of the objects in the real-world problem that you are trying to solve. These objects are called conceptual classes, not software classes, because they represent objects in the problem space, not the solution. In this assignment you will sketch a domain model, illustrating the real-world objects for one of your project use cases. Your supervisor will review the domain model and offer comments to help you to refine your understanding of the use case.

N/A

Data Analysis, ER Diagram, Decisions, Schema

One Week

Reading, Writing, Teaming

Design, Design Specification, Normalization, Requirements Analysis

As a software engineer you will often be required to design the relational schema for an information systems and specify entity-integrity and referential integrity constraints based on the entity relationship diagram (designed as a part of project milestone 1) and the problem statement (written as a part of project milestone 1). Please note that your relational schema must have the ability to store the required data in an efficient manner without any duplication.

A critical ability while working within a team is to develop an ability to manage conflicts, accommodate different design decisions, and manage conflicting client requirements. This milestone helps you apply these abilities in a real life situation.

3

Students are expected to follow ER to Relational Schema design rules and naming conventions as prescribed in the Course Text and as also covered in the class.

CSC 225 – Introduction to Software Development PRELIMINARY TEST PLAN REPORT The project manager has decided to continue development of the product begun but not completed by an acquired company. (This is the product your team evaluated in the Product Review Report, developed customer requirements for in the Customer Requirements Report, developed a prioritized bug/enhancement list for in the Prioritized Bug/Enhancement Report, and evaluated project management tools for in the Project Management Tool Report.) The product manager has assigned your development team to develop a test plan for the top six items on the Prioritized Bug/Enhancement List. Specifically, the project manager wants your team’s recommendation on the following:  Enhancement test plan - a detailed description of each enhancement’s intended behavior and a detailed description of tests that demonstrate the behavior.  Bug test plan – a detailed description of the bug behavior (i.e., bug report) and a detailed description of test that demonstrate the bug has been fixed. Your team’s report needs to recommend tests that will verify that enhancements have been correctly implemented and that bugs have been completely fixed. The project manager has asked your team to make a ten-minute presentation summarizing the report. Your team’s 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 preliminary test plan report. 2. The project manager has asked your team to present significant findings from the preliminary test plan 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. What types of tests will be used during the development process? 2. What tests will be used to verify that each enhancement has been correctly implemented? 3. What tests will be used to verify that each bug has been correctly fixed? 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 you team accurately describe the behavior of an implemented enhancement and a fixed bug? 2. Can your team accurate describe a test plan that verifies that enhancements have been correctly implemented and bug correctly fixed? 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. 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. Identify and accurately describe the key behavior characteristics of an implemented enhancement. 2. Create a set of tests that demonstrates the key behavior characteristics of an implemented enhancement. 3. Identify and accurately describe key behavior characteristics of a fixed bug. 4. Create a set of tests that demonstrates the key behavior characteristics of a fixed bug. 5. Identify the key technical information about enhancements and bugs that the project manger wants when deciding how to test the product. 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 Monday (9/24): Introduction to software testing. Friday (9/28): 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 Preliminary Test Plan Report

Technical Rubric
TECHNICAL ABILITIES Ability
Identify and accurately describe the key behavior characteristics of an implemented enhancement. Create tests for enhancements .

Details
Identify the key behavior of each implemented enhancement Accurately describe the behavior of each implemented enhancement Tests presented for each key characteristic Each test accurately and completely verifies correctly enhancement implementation

Report Section
Test Plan Section

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Lists key behavior for each implemented enhancement Key behavior not listed or non-key behavior listed

Points

Describes each implemented enhancement accurately Test Plan Section Lists tests for each key behavior Describes test for each that verifies key behavior for each implemented enhancement

Inaccurate or incomplete descriptions Key behavior not listed

Identify and accurately describe key behavior characteristics of a fixed bug. Create tests for fixed bugs.

Identify the key behavior of each fixed bug Accurately describe the behavior of each fixed bug Tests presented for each key characteristic Each test accurately

Test Plan Section

Lists key behavior for each fixed bug

Description is inaccurate or incompletes, or is missing for some implemented enhancement features Key behavior not listed or non-key behavior listed Inaccurate or incomplete descriptions Key behavior not listed

Describes each fixed bug accurately Test Plan Section Lists tests for each key behavior Describes test for each

Description is

3

CSC 225 – Introduction to Software Development
and completely verifies correctly fixed bug that verifies key behavior for each fixed bug inaccurate or incompletes, or is missing for some fixed bug features Omits frequently used test or list infrequently used tests Unpersuasive or inaccurate description or fails to describe relationship between product characteristics and testing methods.

Create a test plan summary

Identify commonlyused tests

Summary Section

Lists the more frequently used test

Analyze product characteristics that require commonlyused tests

Persuasively and accurately describes the relationship between product characteristics and testing methods

4

CSC 225 – Introduction to Software Development Preliminary Test Plan 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

Uses correct spelling, grammar, etc. throughout report Writing 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 Concisely and accurately demonstrates key features of user training Concisely and accurately demonstrates significant features of the user training sample

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

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 facctors

Create and informative and useful

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
presentation 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 firsttime 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

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

7

CSC 225 – Introduction to Software Development
each Each task is independent, clearly defined, and contributes to the overall software development task 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 Omitted major topics, time not on task, not enough time to answer

Collaborate effectively on a software development team

Breakdown the software development project into small, independent task

Teaming

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

8

CSC 225 – Introduction to Software Development
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 all questions Team members cannot identify team member strengths or weaknesses

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

Identify skills of each team member

Teaming

Develop trust among team members

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

9



Test Plan

One Week

Writing, Speaking, Teaming

Continuous Quality Assurance

The project manager has decided to continue development of the product begun but not completed by an acquired company. The product manager has assigned your development team to develop a test plan for the top six items on the Prioritized Bug/Enhancement List. The project manager will use your test plan 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.