Agile: Scrum Presentation

22
Going back with the Philosophy and the Practice A day with ME: JOHN BATERN

description

A short presentation about Agile: Scrum. How simple can you understand Agile: Scrum?

Transcript of Agile: Scrum Presentation

Page 1: Agile: Scrum Presentation

Going back with the Philosophy and the Practice

A day with ME: JOHN BATERNA

Page 2: Agile: Scrum Presentation

Manifesto for Agile Software Development

Individuals and interactions Working software Customer collaboration Responding to change

Processes and tools Comprehensive documentation Contract negotiation Following a plan

That is, while there is value in the items onthe right, we value the items on the left more.

Page 3: Agile: Scrum Presentation

The Product Backlog

Page 4: Agile: Scrum Presentation

Specific User/Persona/Role: John BaternaAcceptance Criteria -

Reminder RemarksDesired feature Benefit from implementing the feature

Secure log-in So that the access is registered and secured -List of login of each user-time stamp-IP registration-Let’s use the same Network login

[Usually being discussed with the development team]

John Michael Bien

As a Billing Officer, I want to

record each agency’s contact

person.

So that I can easily identify and

call their contact person just if I

need to inquire something or to

simply inform them of any service

update.

Reminder:

Please make sure I can add the agency’s contact person’s;Full Name. Email, Mobile #, Office # w/local, Address include Country and Position

Make sure it is a required fieldI can add one, two or more contact personsI can update their information anytimeI can delete contact information

Contact person can receive an email notification for any activity in the agency’s profile;Edit or Update of the Agency’s Profile and/or services

-Signature here-

Page 5: Agile: Scrum Presentation

We assess and evaluate the Product Backlog, example Product Backlog below:

Microsoft Excel Worksheet

Page 6: Agile: Scrum Presentation

So we can come up with this;

Page 7: Agile: Scrum Presentation

So that we avoid this;

Page 8: Agile: Scrum Presentation

We monitor our progress by doing this:

We burn all…

Page 9: Agile: Scrum Presentation

Let’s have a short activity in reading a user story

Page 10: Agile: Scrum Presentation

John Michael Bien

As a Billing Officer, I want to

record each agency’s contact

person.

So that I can easily identify and

call their contact person just if I

need to inquire something or to

simply inform them of any service

update.

Reminder:

Please make sure I can add the agency’s contact person’s;Full Name. Email, Mobile #, Office # w/local, Address include Country and Position

Make sure it is a required fieldI can add one, two or more contact personsI can update their information anytimeI can delete contact information

Contact person can receive an email notification for any activity in the agency’s profile;Edit or Update of the Agency’s Profile and/or services

-Signature here-

The objectives are:Identify and clarify the acceptance criteria (Reminder)

Which is/are the In-scope and out-scope itemsPlot the acceptance criteriaIdentify the task that is needed to accomplish the User StoryPlot the identified task and do time (hours) assessment using Fibonacci (1,2,3,5,8,13,21)

Page 11: Agile: Scrum Presentation

We don’t do much of this;

Page 12: Agile: Scrum Presentation

Because of many things like this;

Page 13: Agile: Scrum Presentation

Royce did not use the term "waterfall". Royce presented this model as an example of a flawed, non-working model. This, in fact, is how the term is generally used in writing about software development—to describe a critical view of a commonly used software development practice.

Page 14: Agile: Scrum Presentation

The Business Side

The Technical Side

Page 15: Agile: Scrum Presentation

Technology People

Process

User

CustomerInfrastructure

Business

Business Circle This is my own interpretation - BATERNA

Page 16: Agile: Scrum Presentation

So what is exactly Agile as a methodology?

What the heck am I talking about?

It is a methodology with a variety of approach in a Humane way for doing work in a software development

In software development it never was actually a scientific, manufacturing and engineering approach but a Social approach of being collaborative and treating software development as a new product development.

Agile Methodology was created by a group of people (Developers, QA, Project Managers, Analyst, Designers and Marketing) for the same group of people to benefit with.

Page 17: Agile: Scrum Presentation

What will make us

Technical Expertise

Collaboration

Self ManagementHonesty

Open mindedness

Humility

Simplicity

Transparency

Self Trained

Cross Functional

Timeliness

Initiative

Proactive Humble

Page 18: Agile: Scrum Presentation

What will break us

Neglecting End User Silo thinking

Inflexibility

Too much want with too less benefits

No RecognitionHype

Unrealistic Setting of Goal

Being Impulsive…

Pain glory

Being Impulsive!

Page 19: Agile: Scrum Presentation

Business NeedsIs Priority

SimplificationIterative

Quality

Colla

bora

tion

TransparencyClarity

Agility

FlexibilityDone

Page 20: Agile: Scrum Presentation

Scrum is a group of guys hugging each other supporting and pushing the opposition as try to capture and secure the ball beneath them, the ball must be rolled and passed behind the teams area to win the Scrum.

Page 21: Agile: Scrum Presentation

I.T in the business world

Page 22: Agile: Scrum Presentation

What is the best methodology? This is the wrong question – life is more complicated than this. There is not one best methodology but a toolkit of methods to select.

But if you choose your method you strictly do it right.