Software Engineering II - CEN 6017 Project Deliverables for Spring

Project Deliverables for CEN 6017   This is an iteration-based project, based on a hybrid approach of Unified Process and Scrum using Rational Team Concert as our CLM too.   All artifacts of each Iteration are to be posted in Rational Team Concert (RTC), which is separately documented with accompanying tutorials on my web page.   Each Iteration, which we will call Sprint, will consist of a number of work items that will result in the production of artifacts that must be planned, produced, tested, validated, and deployed incrementally to our clients. 2

Introductory Thoughts and Themes   Agile Methodology: As we discussed last semester, we will be continuing with an Agile-hybrid approach integrating elements of the Unified Process and Agile – Scrum in particular within the context of Team Concert, RTC.   Scrum. Since we will be using Scrum as our management approach, we will talk in terms of Sprints, Product Backlog, burn-down charts, Sprint-backlogs, along with Scrum characteristics such as self-organizing, incremental and iterative development, delivering increments of real, business value each increment and more.   Planning: The continuation of our projects will entail levels of planning starting with a well defined sprint (the one to be undertaken) following by increasing lesser definition and coarser granularity for subsequent springs, but all in concert with an overall “Development Plan.”

Rational Team Concert   Rational Team Concert (RTC) will continue to be the tool of choice for CEN   All work items and artifacts for each iteration will be posted to appropriate places in your team’s project area.   A set of tutorials on RTC has been developed for your use.   Tutorials include basic information on ALM/CLM, creating and managing a Jazz account, creating a new project, managing requirements with Rational Requirements Composer (RRC), creating iterations, work items, establishing the Eclipse client for your use, source control (your programming), change sets, and linking work items and change sets. (More will be coming later.)   Using facilities within RTC for employing Scrum will require a good bit of work to learn and effectively use the guidance and prescriptive features within RTC. Project Management of the Sprints and all that are a part of Scrum are located in Change Management within RTC. More ahead. 4

Team Roles and Responsibilities (suggested roles)   Team lead and backup:   Team Quality Assurance Manager : (responsible for ensuring all work items are properly reported, formatted, included on time and more; responsible for work item reports to RTC)   Software Architect (should be your strongest designer/programmer)   Application Designers (Modelers; architects; UI specialist)   Application Programmers (API / IDE / programmers)   Database Specialists (database designers; interfacing…)   Testing and Assessment (huge job done correctly) 5

Work Items   Each sprint will consist of work items undertaken as part of the current sprint backlog.   Each Work Item will be posted to your project area in RTC, along with the name(s) of the individual(s) primarily responsible for accommodating each work item.   Some of these items may be Word documents, others graphical models, tables, answers to questions, and assessments. Many will be executable code items, test suites, assessment results, and more.   Using RTC for this semester will be a change of pace, and the Scrum pages in RTC must be used to the fullest. 6

Grammar, Wording, and Professionalism   Under NO circumstances will poor grammar or ill-conceived sentences be considered acceptable work. Remember: you only get one chance to make a first impression. Poorly done work will really hurt your grade and perception of what otherwise might be high-quality work. This is a graduate level course and mature, professionalism is expected.   EACH work item of EACH iteration must be reviewed   While the Quality Assurance Manager (ahead) may be the one primarily responsible for grammar and wording, please recognize that this is a TEAM responsibility!!   I cannot stress too strongly emphasis placed on professionalism in organization, content, presenting and reporting. 7

Work Item: Executive Summary   Each Sprint will include an artifact that is the Executive Summary. It should include:   Project Title   Standard contents (see previous generic description) Project lead will develop the Executive Summary   Describe in summary form the work items undertaken for this iteration. (Details will follow and should not be included in this summary)   Include any issues encountered. 8

Work Item: Statement of Work   Each Sprint is to contain a work item delineating the individual team member’s Statement of Work.   This must be posted in with the work items for the specific sprint.   Additionally, individual Peer Reviews must be submitted no later than class time on the date on which the Iteration Reports are due/presented. 9

Work Item: The Sprint   Those items from the sprint backlog (features, scenarios, etc.) implemented within a specific sprint will be included and fully discussed here. Include an Activity Diagram to document flow.   There will be likely multiple individual work-item descriptions to be accommodated.   Burn-down chart, sprint retrospectives, etc. must be included   Assessment to include all details regarding the good, bad, and ugly must be included.   All testing (various kinds) and validation results must be included. More later on this topic. 10

Work Item: Sprint Retrospective   Frank assessment of an iteration (5-10 minutes)   The sprint must be assessed as to what was / was not accomplished, work items produced, work items unresolved and disposition of these.   This is the ‘sprint retrospective.’   This will be included within RTC.   Individual Peer Reviews must be submitted no later than class time on the date on which the Iteration Reports are due/presented.   Likely accomplished by Team Leader 11

Work Item Quality Manager’s Certification   I certify that to the best of my ability all work items have been completed and are included in the iteration report.   _____ Quality Manager’s (QMgr) Signature   _____ Team Leader’s (TL) Signature   Comments optional. 12

Sprint #1- Organization and Planning due: 28 Jan 2013   Executive Summary to include team organization and roles   Statement of Work – lots of planning this time.   Include establshing the management entries in Change Management within RTC. Among other entries, the Product Backlog from Client (Prioritized), burn down chart(s) for current sprint, velocity computed as progress takes place, the story points from the use cases, etc. must be developed by the team. This will require a good deal of total team effort.   The Sprints:   Sprint Development Plan (see slides that follow)   This sprint is essentially a series of Development Plans for management, testing and validation, and planning the individual Sprints from the Product Backlog   Sprint #2 – Plan at fine level; Subsequent sprints at a coarse level at this time. All features must be accommodated.   Sprint Retrospective   QM Certification 13

Sprint #1 - continued Sprint Development Plan  Map out anticipated Sprints to include all functionality from Product Backlog is accommodated. Product Backlog is accommodated.  Note that Product Backlog is rather high level, while use case scenarios are fine grained. If necessary, use the Feature mappings to use case scenarios to identify the product scenarios are fine grained. If necessary, use the Feature mappings to use case scenarios to identify the product backlog entries. backlog entries.  Ensure all use case scenarios trace to the Product Backlog and to anticipated Sprint Backlogs to anticipated Sprint Backlogs  Every scenario from use cases must be accommodated in Sprint planning. Ensure traceability. Sprint planning. Ensure traceability.  Each sprint must include a detailed test plan, test data for validation and development of test suites, retrospective, etc. 14

 Management Planning  Decide on development environment for programming such as Eclipse client and Visual Studio client. as Eclipse client and Visual Studio client.  Study Team Concert and tutorials on Scrum and Builds,...  Undertake a prototype development build and versioning  Study Configuration Management and Versioning in RTC  Testing and Validation  Develop test plan for User Interface from Use Cases Include Validation Criteria for each feature set. Include Validation Criteria for each feature set.  Develop Test scenarios and test suites from Use Cases to test  Test Suites must be planned, developed, and archived for all testing including functional and regression testing. testing including functional and regression testing. The results of this sprint will be presented to the class. The results of this sprint will be presented to the class. 15 Sprint #1 - Thoughts

Architectural Design Decide and design User Interface with clients Design database and refactor database Product Backlog from clients prioritized Features Develop anticipated Sprints and next sprint backlog Develop Test Plan and Test Suites from Use Cases Activity Diagam Management Use Team Concert for managing Scrum (see tutorials) Configuration management toos and versioning control Builds and procedures to use RTC Include product backlog from Features in RTC Include Sprint Backlogs in RTC Burn down list included in RTC How to do Builds etc. 16 Additional Notes

Sprint #2 due date: Thursday, 14 Feb

Sprint #2 Work Items Exec Summary, Quality Control statement Statement of Work. Sprint Retrospective Self-Peer Reviews separately submitted via Blackboard

Sprint #2 Work Items – Sprint Details Under Change Management for your Project, Please include Product Backlog under Current Plans. this includes all features, story points, priority… Sprint Backlog w/story points and their individual tasks allocated to specific Sprints Release Backlog - lists each Sprint / and date with story points and tasks for that specific sprint.

Sprint #2 Work Items Release Need data for Release Burndown, Team Velocity and Story points / iteration Current Sprint: try to track progress Project Details: Under Plans, include Exec Summary, SOW, etc. Under TimeLines: map out the specific sprints including stories to be accommodated within each sprint.

Sprint #2 Work Items Include any updates on any prototyping or redesign of your database and/or User Interface. Include any other items you think important.

Sprint #3 due date: Tuesday, 5 March (more coming) Exec Summary Statement of Work Sprint Details (to be determined by team) Quality Control Certification

Sprint must include specific user stories / task forecast, or scenarios from use cases for this sprint. Each user story / scenario must include corresponding acceptance criteria. For user stories, acceptance criteria must map acceptance criteria to stores/tasks For use case scenarios, test plan must map to scenario. Develop test plan for all stories / scenarios in sprint Include burn-down chart on RTC Use Traceability Matrix for mappings above. Update Release Sprint #3 due date: Tuesday, 5 March

Update Product Backlog Update Sprint Backlog Update Release Backlog Update TimeLines Include Executive Summary Include Statement of Work Include Quality Manager’s Statement Send Individual Peer and Self Reviews Please include any key correspondence from our clients as to how they are going to access / test your releases. Sprint #3 due date: Tuesday, 5 March

Sprint #4 due date: Tuesday, 26 March (more coming) Exec Summary Statement of Work Sprint Details to be determined by team Quality Control Certification

Sprint #5 due date: Tuesday, 16 April (more coming) Exec Summary Statement of Work Sprint Details to be determined by team Quality Control Certification

Sprint #6 due date: Tuesday, 30 April (more coming) Exec Summary Statement of Work Sprint Details to be determined by team Quality Control Certification