Agle Present

7/28/2019 Agle Present

1/34

Project Framework

Loan Performance

June 30, 2009


2/34

2|Type filename here on master page First American CoreLogic Proprietary and Confidential

Topics - Overview

Session 1 Roles and Responsibilities

The purpose of this presentation is to clarify project roles and responsibilities, establish a workingprocess, and set up team working agreements.

The details of fulfilling each work effort can be flexible but the process has to be rock solid

The values that drive behavior:Commitment

Focus

Openness and Transparency

Flexibility and Agility

CollaborationRespect

Courage

Session 2 Agile Scrum Process

What is Scrum

Sprint Events

Scrum Artifacts

Scrum Terminology (Appendix A)

Terminology


3/34


Session 1 - Roles and Responsibilities

Table of Contents

Team Structure

Teamwork-Focus

The Delivery Team

Product Managers

Analytics

Project Managers/Scrum Master

Technology and Engineering Team (Developers, DBAs, Testers)Technical Writers

Data OperationsDelivery Team Advisors


4/34


Team Structure(Roles and Responsibilities)

Delivery Team (The

Core Project Team)

Proj

Manager

Prod

Manager

DBAAnalytics/

Modeler

DevQA

Technical

WritersData Ops

Team

Advisors

Exec

Management

OtherStakeholders

T&E

Management

Prod

Management

Data Ops

Management

Sales

Management

Client

Services

Management

Finance

Management

PMO


5/34


Teamwork Focus(Roles and Responsibilities)

Tech & EngTeam, Analytics,

Data Ops

The DeliveryTeam

(Negotiated)

Product

ManagementOther

Teams

How

Why

What

When


6/34


The Delivery Team(Roles and Responsibilities)

Team responsibilitiesResponsible and accountable

Committed and fully involved in project

Negotiate Delivery/Release/Dates (feature/function/trade-offs)

Meet and own commitments

Own Estimates

Validate Business Goals and deliverables

Participate in Project Meetings

Creative solutions and Collaboration

Self-organize

Cross-functional

Focus on What can be done

Own the scope


7/347|Type filename here on master page First American CoreLogic Proprietary and Confidential

The Delivery Team (Does Not)(Roles and Responsibilities)

Make decision in a bubble. The following are examples ofdecisions not made by the team alone:

Project Framework

Global Architecture

Business Strategy

Capital ExpendituresCompliance

Security

Corporate Policy

Focus on Why it cant be done



Product Managers(Roles and Responsibilities)

Overall Product Responsibilities

Make Product Decisions / Own the ProductOwn the product backlog.

Prioritization

Own when we release (own the Go decision)

Project Responsibilities

Ideation PhaseIdentify potential market opportunities

Conduct market research

Develop business case and provide recommendations on most profitable opportunities

Build PhaseDefine product strategy and product roadmaps

Sets the long-term vision for the product

Create product planDefine packaging and establish pricing in collaboration with sales

Define product requirements (user stories)Manage the product backlog (open items / open requests)

Balance a favorable return on investment with customer needs

Represent the CustomerWork with customers to define product requirements and functionality

Launch PhaseEnable the Organization (Sales, Service, Operations, Finance)



Product Managers (Do Not)(Roles and Responsibilities)

Product Managers do not own the following:Manage how a deliverable will be implemented(T&E Team) - TacticalOwn technology direction (T&E Team) Strategic

Own the Project process (PMO)

Determine delivery Timeline (The Team)



Project Managers/Scrum Master(Roles and Responsibilities)

The overall responsibility of the Project Manager/Scrum Master is to manage process in orderto ensure team goals are met and values upheld.

Are an independent party

Keeper of the ProcessCoach the team

Remove roadblocks (help/prevent/escalate)

Facilitate (Meetings/Work Estimation/Planning)Help the team be successful by facilitating creativity and empowerment

Create an environment that fosters collaborative decision-making

Mediate and Negotiate (Facilitates discussion and conflict resolution)

CommunicationHelp people communicate

Keep information about the team's progress up-to-date and visible to all parties

Escalation

Maintain an environment that supports high productivity

Coordinate project deliverablesManage timelines/quality

Facilitate deployments to Production environments

Manage cross-functional team activities (outside core team)



Project Managers/Scrum Master (Do Not)(Roles and Responsibilities)

Project Manager/Scrum Master Does Not:

Own and prioritize Product Backlog (Product Manager)

Provide business requirements (Product Management)

Own product direction (Product Manager)

Own estimates (Team)

Make delivery decisions (Team)

Have to have all the answers (Team)

Own technology direction (T&E Team)



Technology and Engineering (Developers, DBAs, Testers, etc)(Roles and Responsibilities)

T&E team responsibilitiesTech Team CommunicationsTask Updates

Software and system design and use of frameworks/patterns/services

Coding (new and refactoring old)

Creating & executing unit tests

New Feature/Functional TestingRegression and System Performance Testing

Build/Release Automation

Knowledge growth and application

Collaborates on the establishment of and follows FACL Engineeringsoftware development and testing standards/practices

T&E team does notOwn product direction (Product Manager)

Own the project management process (Project Manager/Scum master)

Determine when a deliverable will be released (The Team)

Own the scope (The Team)



Analytics (Modelers)(Roles and Responsibilities)

Analytics ResponsibilitiesAnalytics Team Communications

Data Pull/Data Acquisition

Data Analysis/Data Exploration/Data Audit

Iterative Modeling/Model development

Feasibility Studies

Regression AnalysisModel Evaluation

Produce reports, graphs, and documentation for Model reviews/Model support

Model Testing

Support Delivery/Deployment with Engineering

Monitoring after deployment (Client/ad-hoc analysis)

Task Updates

Analytics Does notOwn product direction (Product Manager)

Own the project management process (Project Manager/Scum master)

Determine when a deliverable will be released (The Team)




Technical Writers(Roles and Responsibilities)

Technical Writers ResponsibilitiesCreates guides

Data definitions

Report layouts

User reference guide

Technical Writers Do notOwn product direction

Own technology direction

Own the project process



Data Operations(Roles and Responsibilities)

ResponsibilitiesData Acquisition

Data Profiling, Validation and Content Analysis

Data Cleansing and Normalization

Data Mapping to target record layout or database

Data Derivations necessary to create selected information that may need to be createdfrom the combination or content of other fields

Data creation that would feed product flows

Data Quality- in raw and processed points

Data Quality Assurance through product views

May develop tools, processes and production environments for the purpose of completingthe above mentioned activities

May collaborate with Project Management, Product Management and Developers on datarelated issues surrounding product to extent that recommendations might be provided aboutwhich specific fields might be best to use, based on knowledge of source, accuracy ofsource and other decisions that are made during the data creation process.

Data Operations does notOwn product direction




Delivery Team Advisors (Sponsors, Exe. Management, Management, etc)(Roles and Responsibilities)

ResponsibilitiesAssist with strategic planning and forecasting activities

Enable and support the delivery team

Escalation point

Oversees creation and adoption of process, standards, and tools

Mentor and trainStaffing and retention

Provide value focused leadershipHire and build the right teams (build well formed teams)

Advisors do notMake decisions on behalf of the team (The Team)

Determine when a deliverable will be released (The Team)Make daily contributions to the project (The Team)

Disrupt flow of the team



Session 2 - Scrum

Scrum In A Flash:Process

EventsArtifacts

Note: Symbols



Scrum is an agile process that allows us to focus ondelivering the highest business value in the shortest time.

It allows us to rapidly and repeatedly inspect actual working

software (every two weeks to one month). The business sets the priorities. Teams self-organize todetermine the best way to deliver the highest priority

features.

Every two weeks to a month anyone can see real working

software and decide to release it as is or continue to enhanceit for another sprint.

What is Scrum?



More About Scrum

Scrum Characteristics

Self-organizing teams

Product progresses in a series of sprints

Requirements are captured as items in a list of product backlog

No changes during a sprint

No specific engineering practices prescribed

Uses generic rules to create an agile environment for deliveringprojects

Sprints

Scrum projects make progress in a series of sprintsTypical duration of a sprint is 24 weeks or a calendar month at most

A constant duration leads to a better rhythm and metrics

Product is designed, coded, and tested during each sprint


20/34


Scrum: Putting it all together

30 days

DailyWeekly

Product Backlog

As prioritized by Product Owner

Sprint Backlog(group of items

to be completed)

Backlog tasksexpanded

by team

Potentially Shippable

Product Increment

Status

Meetings

Review MeetingDemo features

Metrics

Note: Backlogs, tasks and progress are tracked in Version One tool


21/34


Scrum: Sequential vs. overlapping development

Rather than doing all ofone thing at a time...

...Scrum teams do a little of

everything all the time

Requirements Design Code Test


22/34


Story Time/Backlog Grooming

Prioritized

Product

backlog

Sense of

requirements

Technology

Scrum Events: Backlog Grooming

Regularly scheduled

Involve the entire delivery team

Discuss and groom the backlogCan start at high level with epics (functionality is often largerthan will fit in one sprint)

User stories - BacklogsAssign Story points (Velocity can be calculated from storypoints. Velocity measures how much the team can accomplishduring a certain timeframe.)

Add new backlogs (if applicable)

Split backlogs (if applicable)

Work though the queue of backlogs in preparation

for future work


23/34


Sprint

Backlog/

Commitment

Sprint

goal

Sprint planning meeting

Sprint prioritization

Analyze and evaluate productbacklog

Select sprint goal

Sprint planning

Decide how to achieve sprint goal(high-level design)

Team selects items from theprioritized product backlogs theycan commit to completing

Tasks are identified and each isestimated (1-16 hours)

Business

conditions

Teamcapacity

Prioritized

Product

backlog

Technology

ProductRoadmap

Scrum Events: Sprint Planning


24/34


Scrum Events: More About Sprint planning

Sprint planning is a collaborative process (not done alone by theScrumMaster or Leads).

Example of backlog item broken down into tasks:

As a vacation planner, Iwant to see photos of thehotels.

Code the middle tier (8 hours)

Code the user interface (4 hours)

Write test cases (4 hours)

Update performance tests (4

hours)


25/34


On time

Daily

15 Minutes

Stand-up

Collaborative

Scrum Events: The daily scrum

Parameters

Not for problem solving Sprint

Sprint team is invited

Only team members, ScrumMaster,product owner, can talk

Helps avoid other unnecessarymeetings

What did you do yesterday?

1

What will you do today?

2

Is anything in your way?

3

Everyone answers 3 questions

These are notstatus for the

ScrumMasterThey are commitments in front ofpeers


26/34


Scrum Events: The sprint review

Team presents what it accomplished during the sprintTypically takes the form of a demo of new features or underlyingarchitecture

Informal

2-hour prep time rule

Overview of the sprintSprint Metrics

Live working Demo

Whole team participates

Invite the world


27/34


28/34


Scrum Artifact : Product backlog

The requirements

A list of all the desired work for the product

Ideally expressed such that each item hasvalue to the users or customers of the product

Prioritized by the Product Manager

Reprioritized at the start of each sprint byProduct Manager


29/34


Scrum Artifact : A sample product backlog

Backlog item Estimate

Allow a guest to make a reservation 3

As a guest, I want to cancel a reservation. 5

As a guest, I want to change the dates of a reservation. 3

Improve exception handling 8

... 20

Backlog in story points (Story point = point of reference)

For example: If I am in Santa Ana, CA (USA) traveling to Disney Land (Anaheim,CA) the trip is about 10 miles (actual 9.6). If I was traveling to New York City thetrip would be about 2,800 miles (Actual 2,772). I could assign the Disney Trip a 3and maybe the New York Trip a 20. Around the world maybe 100(?).


30/34


Scrum Artifact : The sprint goal

A short statement of what the work will be focused on duringthe sprint

Database Application

Financial services

Real Estate Trend

Support features necessary for

forecasting HPI for next 6, 12 ,

18 months.

Support more technicalindicators than company ABC

with real-time, streaming data.

Make the application run on

SQL Server in addition to

Oracle.


31/34


Hours

40

30

20

10

0

Mon Tue Wed Thu Fri

Tasks

Code the user interface

Code the middle tier

Test the middle tier

Write online help

Mon

8

16

8

12

Tues Wed Thur Fri

4

12

16

7

11

8

10

16 8

50

Scrum Artifact: Daily hours update & burn down

chart

44

34

18

8

32

44 32 34 18 8


32/34


Scrum Terminology

Scrum Terminology (Appendix B)


33/34


Scrum Terminology

Agile development: Iterative Development where requirements and solutions evolve through collaborationbetween self-organizing cross-functional teams.

Self Organizing: The team organizes themselves and decides between themselves, owns and meetcommitments.

Scrum: In game of Rugby, where the whole team "tries to go to the distance as a unit, passing the ball back andforth" showing team work

Sprint: A time period (typically between two weeks and one month) in which development occurs on a set of

backlog items that the Team has committed to.

Backlog: The product backlog (or "backlog") is the requirements for a system, expressed as a prioritized list ofproduct backlog Items. These included both functional and non-functional customer requirements, as well astechnical team-generated requirements. While there are multiple inputs to the product backlog, it is the soleresponsibility of the product owner to prioritize the product backlog. During a Sprint planning meeting, backlogitems are moved from the product backlog into a sprint, based on the product owner's priorities.

Product Backlog Item: In Scrum, a product backlog item is a unit of work small enough to be completed by ateam in one Sprint iteration. Backlog items are decomposed into one or more tasks.

Task: A sprint task (or task) is a unit of work generally between four and sixteen hours. Team membersvolunteer for tasks. They update the estimated number of hours remaining on a daily basis, influencing the sprintburndown chart. Tasks are contained by backlog items. Scrum literature encourages splitting a task into severalif the estimate exceeds twelve hours.


34/34

Scrum Terminology Cont.

Burndown: Each team member is responsible for logging his/her hours remaining per task each day in thetracking tool (Version One). As a result, the hours for each task will reduce daily. The result of the daily entries

of the team will be reflected on the Burndown Chart for the sprint.

Burndown Chart: The burndown chart is a "big picture" view of a progress of the team. It shows how muchwork is left to do. This information is obtained from daily VersionOne updates by the team to reflect their To Dohours per task.

Velocity : The amount of work in story points each team can handle for a defined sprint timeframe. This can be

estimated by viewing previous sprints, assuming the team composition and sprint duration are keptconstant. Once established, velocity can be used to plan projects and forecast release and product completiondates.

Stand-Up Meeting: A fifteen-minute daily meeting for each team member to answer three questions:

"What have I done since the last Scrum meeting? (i.e. yesterday)"

"What will I do before the next Scrum meeting? (i.e. today)"

"What prevents me from performing my work as efficiently as possible?

Impediment:Anything that prevents a team member from performing work as efficiently as possible.

Retrospective: The sprint retrospective meeting is held at the end of every sprint to discuss what went well,challenges and what to improve in the next sprint.

Date post:	03-Apr-2018
Category:	Documents
Upload:	kodanda
View:	220 times
Download:	0 times

Agle Present

Documents