Object-Oriented

Programming: Design
Patterns
•Ma. Diane S. Rivera
•11-17-2014

1 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Training Objectives

Describe the purpose and uses of design patterns

Understand creational pattern concepts in order to help make systems

independent of how its objects are created

Understand structural pattern concepts in order to compose classes and

objects into larger structures

Understand behavioral pattern concepts in order to manage algorithms and

assign responsibilities to objects

2 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile Manifesto

"We are uncovering better ways of

developing software by doing it and
helping others do it."

3 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile Manifesto

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

4 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

5 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

6 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

7 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

8 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

~ Scrum is an agile process that allows us to focus on

delivering 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).

~ Time-boxed and Never Extended

9 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Characteristics:
- Self-organizing teams
- Product progresses in a series of two- to four-week “sprints”
- Requirements are captured as items in a list of “product backlog”
- No specific engineering practices prescribed
- Uses generative rules to create an agile environment for delivering
projects
- Inspect and Adapt

10 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

11 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Roles

•Product owner
•ScrumMaster
•Team

12 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Owner
What ~What

-Responsible for maximizing ROI -Not the same as a Product Marketing

Manager
- Knows the product by heart
- Not responsible for maximizing ROI
- Maintains the product backlog in terms of commercial product

- Responsible for explaining to the team what is in the product backlog

- Help achieve the highest business value of the product

13 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Team
What ~What

- Cross functional -There is no hierarchy in the team,

everyone is EQUAL
- Self managing/ Self organizing
-Should not be involved in other
- Multi learning projects

- Develops the project, composed of 7(±2) members

- Create the sprint backlog
- Provide ideas to the Product Owner on how to make the product much better

14 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Scrum Master
What ~What

Facilitates the scrum process -Does not assign task

- Serves the team -Is not the MANAGER!

- Removes impediments -Cannot be the same as PO

Should not be part of the Dev team

- Makes sure that the team, PO and stakeholders know the principles of scrum
- A coach and a teacher
- 80 to 90% social skills

15 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Stakeholders
What ~What

-Can be the customers, managers -Cannot dictate the team

and end users

- Supports the team

- They make their expertise

available

16 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Artifacts

•Product backlog
•Sprint backlog
•Burndown charts

17 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog

- exists (and evolves) over the lifetime of the project

- product roadmap
Good Characteristics:
1. clear and sustainable
2. fine - grained
3. well – estimated
4. emergent
5. prioritized

18 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog

19 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog

- output of the Sprint Planning

- list of tasks to be done by the Team in a Sprint
- work is never assigned to anybody

20 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog

21 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog (Scrum Board)

22 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Burndown Chart

- Used to track the progress

- Remaining estimate of work remaining against number of days

- Ideally should be a downward sloping graph

- More effective if written in a board

23 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Burndown Chart

24 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Ceremonies

•Definition of Done
•Sprint Planning
•Sprint Review
•Sprint Retrospective
•Daily Scrum Meeting
•Product Backlog Refinement

25 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Definition of Done
What Who

-Output per iteration is potentially PO, Team, SM

shippable product

-Should be discussed before the

Sprints start
Duration:
- Purpose is to minimize delay and Depends on the team
risk

-Can be in a form of a document

26 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Planning Part 1
What Who

- Preparation for sprint PO, Team, SM

- What? and Why? by PO
- Create the Sprint Goal

Duration:
1 hour per week of sprint

27 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Planning Part 2
What Who

- Preparation for sprint Team, SM

- How? by Team PO (optional)
- Contains estimates, depends on
the team what is defined number
of hours per day
Duration:
-Forecast of what can be done
(Sprint Commitment) 1 hour per week of sprint but not more
-Poker planning than 4 hours

28 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Daily Scrum / Daily Standup Meeting
What Who

- Update between the members Team

- Answer 3 questions: PO (optional) , SM (optional),
What is DONE? (What have you stakeholders (optional)
done YESTERDAY?)
What will be DONE? (What will
you do TODAY?) Duration:
Impediments (What are the
PROBLEMS you have 15 minutes
encountered?)
- Follow up meeting is encouraged
if there are unclear tasks

29 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog Refinement
What Who

- Split big items, analyze, re PO, Team, other experts that can help
prioritize,

-It is not for the items currently

handled by the team
Duration:
-Time for analysis of future PB 10% of the capacity of the team for
items that sprint

30 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Review
What Who

- Coined to a “demo” but not really PO, Team, SM

Stakeholders (optional)
-No ppt presentations!!

- End users will use the system not

Duration:
the team
1 hour per week of sprint
-Inspect and adapt (product level)

31 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Retrospective
What Who

-Inspect and Adapt (Process and Team, SM

Environment level) PO (optional), Stakeholders (optional)

-What is working and what’s not

Duration:
45 minutes per week of sprint

32 © Nokia Solutions and Networks 2014

<Change information classification in footer>
33 © Nokia Solutions and Networks 2014
<Change information classification in footer>