software eng

Mid-Term Team Project Report

DUE: Midnight Wednesday March 21

(all submission deadline rules apply – exceptions will be considered on a case-by-case basis)

ASSUMPTION:

· Your team is considered a Scrum team.

· This means your team is self-governing and all decisions regarding internal working structure of the team are made in collaboration with team members.

· All team members participate and collaborate with other members of the team.

· This means the team is responsible to maintain working harmony among team members and make certain that action of one team member does not negatively impact the output of the team.

· All team members contribute based on their assigned responsibility within the team.

· This means if a team member does not contribute as much as other team members then it is the responsibility of the rest of the team to decide if that team member shall remain part of the team. Note that a large portion of your Team Project grade is depended on the collective work of individual team members.

VISION:

Education web platform which allows students to specify their desired degree and preferred University in order to determine the optimal course curriculum to graduate in the shortest amount of time. The platform would use GPS to identify near-by community colleges in which to augment the students schedule in order to reduce cost or time-to-completion. Additional pay functionality would allow a student to schedule course notifications, adjust classes based on personal preference, and pre-register at supporting Universities.

TOOLS:

· Behavior Driven Development Methodology (BDD)

· User Story – How to address the need of your user

· Persona – User Role, User Persona, User Journey

· Acceptance Criteria – Header & Scenario in BDD

· Fundamentals of Software Project Management

· Use Case, Sequence Diagram & Swimlane Diagram, Activity Diagram, etc.

Prerequisite:

Submission of, at least, 4 personas prior to submission of your Project report

YOUR TASK:

Submit a preliminary report of your project progress. Your submission will be an informal report on:

· Project discovery – who are your stakeholders, what are their needs, what your team can delivery to address their needs based on your preliminary knowledge of their pain points, preliminary estimation of cost in term of work-effort (not $$ value at this point), team structure, technology/platform needed to deliver the product, high-level project plan to deliver the product.

· HINT:

· For the purpose of this course, your stakeholders are fictitious but you need to indicate who they may be and propose how you plan to get input (you won’t have to actually go through your proposal.)

· Write a reasonable number of User Stories that shows you understand the need of your stakeholders (at this stage 10-12 user stories will be sufficient)

· Based on your User Stories, write Acceptance Criteria for the stories (at this stage pick writing acceptance criteria for 5 stories will be sufficient – so, pick at least 5 “more complicate” user stories and write acceptance criteria for – header and scenarios.)

· Propose technology platform and tools that you may need to create this product.

· Your report shall include Use Case and sequence diagram to indicate your preliminary design and its interaction with the user (at this stage 2 Use Cases and one Sequence diagram will be sufficient – Activity Diagram will be extra credit for the team but not required.)

· Your report should include a high-level project plan. This plan should include:

· High-level tasks

· Sub-activities related to the high-level tasks (based on your preliminary knowledge at this point)

· Proposed delivery phases and proposed sub-activities timeline for delivery (these would roll up to their respective high-level tasks)

· Resource and effort requirement for delivery of the product at each phase – remember this will be a high-level estimate based on your preliminary knowledge of the stakeholder need and project requirements.