Agile definitions

Releases cover limited scope of the overall project:

-Release structure -Define teams -Manage overall backlog

Requirement sign-off

-at end of definition phase -client sign-off on story completeness and accuracy

Solution Acceptance sign-off

-at end of sprint cycle -client sign-off on developed feature-ensuring development meets the needs

user acceptance testing

An independent test performed by end users prior to accepting the delivered system -UAT: a process that confirms that the output of a project meet the business needs and requirements

scrum

Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal -describes a set of meetings, tools, and roles that work in concert to help teams structure and manage their work

backlog grooming

When the product owner and some, or all, of the rest of the team refine the backlog on a regular basis to ensure the backlog contains the appropriate items, that they are prioritized, and that the items at the top of the backlog are ready for delivery. -removing user stories that no longer appear relevant -creating new user stories in response to newly discovered needs -re-assessing priority of stories

Who is Responsible for Status Change: In Progress

Dev Team

Who is Responsible for Status Change: Ready for Tech Review

Dev Team

Change Control for Major Changes

1. Change in scope or enhancement identified -by core or extended KY team -by MTX team 2. Change or enhancement documented in project management tool -by MTX team -create story and add to Backlog Release and LOE estimated based on design considerations 3. Assess priority and business impact against level of effort -MTX team in collaboration with PA team will evaluate and prioritize requests for change against release plan 4. Determine whether to include scope of current release -decide whether to keep in backlog or move to current release -possibly do a '0 LOE' exchange for other functionality in upcoming releases and sprints 5. Communicate decision to the requestor and other stakeholders 6. Implement agreed upon changes -MTX team to finalize design and implement agree-upon changes

Change Control for Minor Changes

1. Change in scope or enhancement identified -by core or extended KY team stakeholders -by MTX team 2. Change or enhancement documented in project management tool -by MTX team -created as a new story to evaluate LOE and impact to overall release plan -enhancements and change that will take minutes should be added in AC with timestamp/initials and as Issues 3. Assess priority and business impact against level of effort -MTX team in collaboration with PA team will evaluate and prioritize requests for change against release plan 4. Determine whether to include scope of current release -decide whether to move to backlog or move to current release or sprint -possibly do a '0 LOE' exchange for other functionality in upcoming releases and sprints 5. Communicate decision to the requestor and other stakeholders 6. Implement agreed upon changes -MTX team to finalize design and implement agree-upon changes

What are delivery project phases and deliverables?

1. Kick-off: Discovery, Define and Design 2. Dev Start: Sprint Development 3. UAT Start: Testing & Training 4. Go Live: Post Go Live Support

how long do sprints last?

2 weeks

Acceptance Criteria

A critical part of the story describing requirements which an implementation should satisfy to be accepted by a user or customer. -Baseline for creating the test cases for QA/test team. -Baseline for creating the task for the development team. -This serves as the exit criteria for stories to be implemented & tested completely and finally accepted by the end users.

level of effort

An activity that does not produce definitive end products and is measured by the passage of time.

Story description

A high-level objective/requirement of a user story. Eg. "As a sales rep(WHO), I need to be able to capture details of client contacts (WHAT) so that I can use CRM as a master repository of sales contacts. (WHY)".

product owner (PO)

A person who represents the project stakeholders and is responsible for communicating and aligning project priorities between the stakeholders and development team. -a member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to streamline the execution of program priorities while maintaining the conceptual and technical integrity of the Features or components for the team

backlog

A prioritized list of features or user stories to add to a program -decision-making artifact that helps you estimate, refine and prioritize everything you might sometime in the future want to complete

Who is Responsible for Status Change: Complete

BA/Client

Who is Responsible for Status Change: UAT Complete

BA/Client

Who is Responsible for Status Change: Planned

BA/PM

Who is Responsible for Status Change: Backlog

BA/PM/Tech Lead

Who is Responsible for Status Change: Blocked

BA/Tech Lead

Who is Responsible for Status Change: Duplicate

BA/Tech Lead

Who is Responsible for Status Change: New

BA/Tech Lead

Who is Responsible for Status Change: Cancelled

BA/Tech Lead/Client

What happens during Discovery, Define & Design?

Client Kickoff Discovery sessions User Stories Data migration inventory Process flow diagrams Configuration workbook baseline Data Dictionary baseline ERD Integration architecture Development Tasks Sprint plan Test case development UX/UI designs Blueprint/Roadmap Weekly status reports Customer satisfaction surveys

Story Status: UAT Complete

Client validates story ensuring it meets all requirements. All issues have been resolved. Story is ready for production deployment.

What happens during Sprint Development?

Functional dev execution Integration dev execution UX/UI development Data migration loads Test case execution Sprint demos Training plan Training materials development Technical documentation Data Dictionary finalized Configuration workbook finalized Weekly status reports Customer satisfaction surveys

Story Status: Ready for Tech Review

Implementation completed by dev team and is awaiting technical lead's review

Story Status: In Progress

Implementation of tasks has started and is in progress

What happens during Post Go Live Support?

Production bug fixes Agreed upon enhancements Documentation handover Future phase planning

Who is Responsible for Status Change: QA Complete

QA

Who is Responsible for Status Change: QA in Progress

QA

Story Status: QA in Progress

QA team is currently in progress of executing test cases for the story

What is story grooming?

Refinement of story details and Criteria of Acceptance. The primary purpose of a backlog grooming is to ensure the next few sprints worth of user stories in the product backlog are prepared for sprint planning and development. -Main objective of Discovery and Define phases -It is a recurring activity that continues during sprint development -Tries to close out any gaps in story definition -Ensures any new requirements are captured

Story Status: Cancelled

Requirements are no longer valid or needed

user stories

Requirements of new software systems or products as they are implemented in an Agile Development Model. Usually they consist of a few sentences that describe how a consumer would interact with the system or product and what the ideal functionality would look like. These are used to inform the developers of how a system or product should work while they are designing a given portion of the system.

Story Status: Complete

Story components moved to production.

Story Status: Planned

Story has been prioritized and assigned to specific sprint

Story Status: Ready for QA

Story has been reviewed by tech lead and is ready for QA team testing

Who is Responsible for Status Change: Ready for QA

Tech Lead

Who is Responsible for Status Change: Ready for UAT

Tech Lead/QA

Story Status: Ready for UAT

Testing complete and all QA-identified issues have been resolved. Story components are ready for move to UAT environment for client to test.

Story Status: QA Complete

Testing has been completed test cases

Story Status: Blocked

The implementation is blocked due to open requirements or technical dependencies

Story Status: Duplicated

The requirements is captured by another story - this story is a duplicate

Story Status: New

The story is a 'draft' pending client review and assignment into backlog or any sprint

Story Status: Backlog

The story is reviewed by client and approved for implementation but not yet prioritized and assigned to any sprint

What happens during Testing & Training?

UAT deployment Issue fixes Training execution Production Deployment User Acceptance Testing Solution Signed Off Weekly status reports Customer satisfaction surveys

standup

a daily meeting that involves the core team: product owners, developers, and the scrum master

release

a deployable software package that is the culmination of several iterations -can be made before the end of an iteration

velocity

a measure of the amount of work a team can tackle during a single Sprint and is the key metric in scrum -calculated at the end of the sprint by totaling the points for all fully completed user stories

sprint planning

a meeting where the PO describes the highest priority features -an event in the Scrum framework where the team determines the product backlog items they will work on during that sprint and discusses their initial plan for completing those product backlog items -assign user stories to sprint from backlog -assign development tasks to team -manage team velocity

estimation

a quantified evaluation of the effort necessary to carry out a given development task; this is most often expressed in terms of duration -obtain an indication of the overall duration, effort or cost of a software project

sprint

a short, time-boxed period when a scrum team works to complete a set amount of work

iteration

a time box during which development takes place, the duration of which may vary from project to project, usually between 1 and 4 weeks -sprint planning

personas

an archetypical user of a system, an example of the kind of person who would interact with it -if you want to design effective software, then it needs to be designed for a specific person

enhancement

any change or upgrade that increases capabilities beyond the previous state

Predictability

checkpoints along the way to ensure predictable timelines and budget

Stakeholders Engagement

ensure stakeholders are engaged throughout project and are integral part of the process

story grooming

ensure the next few sprints worth of user stories in the product backlog are prepared for sprint planning -when the PO review items on the backlog to ensure the backlog contains the appropriate items, that they are prioritized and that the items at the top of the backlog are ready for delivery

Incremental Development and Releases

from concept, through mockup & prototype to developed solution working with client on iterative improvements

Quality Assurance (QA)

gathering and evaluating information about the services provided as well as the results achieved and comparing this information with an accepted standard -a systematic process that ensures product and service excellence -examines the requirements to design, develop, and manufacture reliable products whereby increasing client confidence, company credibility and the ability to thrive in a competitive environment

during the sprint

incremental developments are demonstrated to the project stakeholders for validation

LOE

level of effort

sprint kickoff

marks the official start of each sprint

A release plan acts as a

project's map, providing context and direction on product goals, vision, and expectations

Transparency

provide full client visibility into requirements and progress of development and testing

Agile planning breaks down the development process into stages called

releases

one iteration of a continuous development cycle

sprint

________ determines the product backlog items that will be worked on during sprint cycles

sprint plan

Speed

start development quickly, validate completed functionality with client and move to next epic

what happens at the end of a sprint?

team holds a sprint review to validate completed work and in collaboration team decides on next steps

sprint demos

traditionally held at the end of a sprint, they show internal stakeholders what's been done and how things work -opportunity to get feedback and receive questions from other team members -teams can share insights, and begin thinking about what will go into the next sprint

Focus on Business Value

while collaborating with client, focus on delivering business value and ensuring client satisfaction with end product