WELCOME

April 1

8, 2023

1

Introduction Brief about SCQAA for new comers Any job openings

Presentation by Kevin Graves

AGENDA

April 1

8, 2023

2

AGILE /

SCRUM

3.23.1

1 - SCQAA-S

F – K

EVIN G

RAVES

• SCQAA-SF www.scqaa.net chapter sponsors the sharing of information to promote and encourage the improvement in information technology quality practices and principles through networking, training and professional development. 

• Networking: We meet once in 2 months in San Fernando Valley.

• Check us out on LinkedIn (SCQAA-SF) http://linkd.in/e2HLn2

• Contact Sujit at sujit58@gmail.com or call 818-878-0834

ABOUT SCQAA-SF- A NOT-FOR PROFIT ORGANIZATION

April 1

8, 2023

4

AGENDAWhy Should You Care?

What is Agile?

What is Scrum?

What Real Scrum Feels Like

Scrum Challenges

Scrum Benefits

AUDIENCE CHECK

WHY SHOULD YOU CARE?Times are Changing It Could Help Your Current Project It Could help You Land Your Next Job It’s Often More Rewarding Work

WHAT IS AGILE?

IT’S NOT WATERFALL WHERE… Long Projects have distinct and sequential Phases

Requirements -> Design -> Programming-> Testing -> Release

Big up-front effort to collect Requirements Multiple Hand-offs between Departments Changing Requirements are discouraged Working Product is available only at the end of the

Project Projects are often cancelled with nothing to show Software is released and the Customer doesn’t like it Team members become demoralized

PROBLEMS WITH THE WATERFALL SDLC Assumes that creating software is like an assembly line Assumes the customer knows exactly what they want

up front Doesn’t engage the customer during development Delivers value to the business too late Doesn’t allow the business to respond to changing

demands Produces artifacts that don’t provide sufficient value Encourages the blame game and politics Doesn’t leverage the best out of team members

WHAT IS AGILE?

AGILE METHODOLOGIES PROMOTEManagement processes that encourage frequent inspection and adaptation

Leadership philosophy that encourages teamwork, self-organization, and accountability

Engineering best practices that allow rapid delivery of high-quality software

AGILE VALUES & PRINCIPLES Individuals and interactions are more important than processes and tools

Working software is more important than comprehensive documentation

Customer collaboration is better than contract negotiation

Responding to change is better than following a plan

HOW SCRUM RELATES TO AGILE Scrum (project management)

Most common Agile implementation Easiest to learn This is my focus tonight

Extreme Programming (technical practices)

Lean (business re-engineering)

KEY SCRUM CONCEPTS An empowered, cross-functional, and self-organizing team of

5-7 individuals are picked to design/build/test software together as one team.

The Business nominates a single Product Owner which identifies and stack-ranks high level business requirements.

The Team works with the Product Owner to breakdown requirements “just in time” into small client-focused “User Stories”, which could each be designed, developed, tested and potentially released within a 4 week “Sprint”.

Aggressive collaboration between team members and the Product Owner works out details within the Sprint on the fly.

Completed work is demonstrated after each Sprint to get feedback and allow the product to evolve to something the Customer finds highly desirable.

SCRUM ROLESProduct Owner

Individual empowered by the company to represent the the priorities of all stakeholders

Identifies the “what” to be done in a Sprint

Scrum Master Ensures everyone is following the process & playing by the

rules Helps remove roadblocks that the team can’t

Team 5-7 empowered individuals with all the skills required to

design, program, and test the product Determines “how” to get something done

SCRUM MEETINGSSprint Planning

Team plans the next 4 weeks of work together

Sprint ReviewTeam shows what they built and solicits feedback

Sprint RetrospectiveTeam identifies ways to improve at the end of each sprint.

Daily ScrumDaily sync-up of the team to stay focused and productive.

SCRUM ARTIFACTS Product Backlog Sprint Backlog Burndown Chart

WHAT REAL SCRUM FEELS LIKE• Work is More Enjoyable

• You feel a greater sense of Ownership

• You feel a greater sense of Creativity

• You feel great being on a highly functional team

• You get a chance to “win” as a team each 3-4 weeks

• You Learn more about how to create software

• You are proud of what you build

SCRUM CHALLENGESEducation of team and others

Buy-in from Team and Management

Flexible Architecture is difficult

Long-term Estimating & Planning

Team empowerment

Requires strong team members

Requires Discipline

SCRUM BENEFITSBetter end product

Earlier delivery of value to customers

Less waste / more productivity

Happier Employees

Less risk of a big failure

More flexible to changing priorities

RESOURCESScrum and XP from the Trenches (Henrik Kniberg) *

Succeeding with Agile (Mike Cohen)

Agile Testing: A Practical Guide for Testers (Janet Gregory)

User Stories Applied (Mike Cohen)

Extreme Programming Explained (Kent Beck)

QUESTIONS?

KEVIN@

KGRAVES.C

OM