Software Engineering - Team Project using Agile and Scrum:

Use this Tracking Scrum Workbook.

Form a Team Team should have 3 - 6 members. Name your team. Identify a coordinator for the team, and specific skill set each member brings to the team.

Identify a domain

For your project identify an industry/domain (ex. Health Care, Finance, Insurance, Transportation, Entertainment, Education, Public Services, …).

Problem Description:

Write an opportunity statement for a Software Engineering Project that involves an enterprise in a specific industry. The project should address the current processes/scenarios (which is tedious and error prone). The problem description and the solution should be clear and targeted (no more than 1 page long – single spaced, font size 12). Would be helpful if you had a member with experience from the industry

The broad goals of the requested software solution, intended to alleviate the issues, should serve multiple participants (actors) and their multiple needs (use cases). Also, describe the general system performance requirements to extend/scale the usability soon.

Though the ultimate description and goal of the project should be broad and far-reaching, the SDLC process will be used to undertake defined tasks over multiple sprints in an incremental way.

Defining Vision and Scope:

Develop the Vision and Scope Document – that describes the problem statement, the features, business objectives, and success criteria. Also, include the list of users and uses (that contribute to the features) and any assumptions and risks to keep in mind through the project. Develop the prototype. Use-case diagrams for principals to relate to the software.

Create UC diagrams and Prototype UI for demonstration and Approval of V&S.

Setup Initial Product Backlog:

Develop a list of users and use cases. Prioritize (Must, Should, Could). For each of the users – list functional requirements. Identify and list non-functional requirements.

Plan, start, and execute Sprint I.

Analysis and Design for Implementation and Change:

Document the software architectural block diagram of the components (birds eye view) of the software. Based on analysis develop the initial design – class diagrams and sequence diagrams for implementation. Develop tasks to implement and test – Sprint I.

Demonstrate. Present your product with the artifacts – complete Sprint I.

Repeat: Review and update product backlog. Select additional actor and use cases. Plan, start, and execute Sprint II.

Demonstrate. Present your product with the artifacts – complete Sprint II.

Repeat: Review and update product backlog. Select additional actor and use cases. Plan, start, and execute Sprint 3.

Demonstrate. Present your product with the artifacts – complete Sprint III.

Repeat: Review and update product backlog. Select additional actor and use cases. Plan, start, and execute Sprint IV.

Demonstrate. Present your product with the artifacts – complete Sprint IV.