Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Don't Lose Your Head With Agile: Choosing The Right Approaches For A Software Project

Agile is not a fashion trend. Agile is here to help software owners achieve product delivery the way their businesses dictate it. Agile has a different face for every project, since every project is unique itself.
by

Your Prezis

on 24 May 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Don't Lose Your Head With Agile: Choosing The Right Approaches For A Software Project

The dark side
of cookies
Anastasia Berestovaya
...and a lot of others
Onward to production!
Agile is not for mere formalities.
Mind the challenges!
Don't Lose Your Head With Agile:

Choosing The Right Approaches
For A Software Project

5 years in IT
over 30 diverse projects
3 years in project management
Agile

methodology
Delusions about Agile
What are people using?
The statistics for past 3 years
The most
popular
Agile
methodologies:
WATERFALL
Prince2
RUP
p
u
r
e
iterative
Agile ideology
SCRUM
Kanban
XP
Lean
Six Sigma
Critical
How to decide
what fits you better?
Any project gets
the processes it deserves
Your future product: let's look through the main criteria
How stable and complete are your requirements?
The scope is clear and fixed

The scope is fixed,
but changes are possible

No clear vision,
high-level epics

No requirements,
ongoing tasks
Kanban
Waterfall
RUP
Six Sigma
Prince2
RUP
Six Sigma
Prince2
SCRUM
Kanban
XP
Lean
SCRUM
Kanban
Six Sigma
Spiral
Crystal
Who are the end users of your system?
Controlled group
Dispersed group
Waterfall
RUP
Six Sigma
Crystal
Spiral
XP
Lean
SCRUM
Kanban
What limitations
does your project have?
RUP
XP
Lean
Crystal
Waterfall
Prince2
SCRUM
Kanban
Timeline
fixed deadline
no deadlines
Six Sigma
XP
Lean
Crystal
SCRUM
Kanban
RUP
Waterfall
Prince2
Spiral
intermediate deadlines
XP
Budget:
fixed
not fixed
Critical
Path
small (<1000 h)
medium
(<10000 h)
big
(>10000 h)
Waterfall
RUP
Lean
SCRUM
Lean
Kanban
Crystal
RUP
Spiral
Crystal
Prince2
SCRUM
Kanban
What type of contract
do you have?
Time & Material
Fixed Cost
Waterfall
RUP
Prince2
Dedicated Team
SCRUM
Kanban
Lean
Lean
Kanban
Crystal
SCRUM
What kind of project do you have?
Startup
Enterprise
Internal
Business
Support
XP
Lean
Spiral
SCRUM
RUP
Lean
Kanban
RUP
Crystal
SCRUM
Kanban
Six Sigma
Crystal
The most popular Agile techniques:
• work hard to identify problems
• try different approaches to solve them
• remember that the same methods
won't work for every case
Daily standup:
Short iterations:
Excessive detalization
of stories
• complicates work with the backlog
Retrospective:
• there is always someone else to blame
Frequent delivery
and active user involvement
• excessive change requests
My favorite ingredients
for effective project management
Daily standup
Short iterations
Prioritized backlogs
Task-board
Demo
Kanban
with intermediate
deadlines
Just a little about freedom...
Find
your perfect
management
balance
Thanks for attention!
Feel free to get in touch:
• just formal, with one person
• becomes the speech of the one star
• grows into a 2-hour meeting
• big features get split into different iterations
• defects get moved to the next sprint
• cause delays at the start of a new sprint
• bloats the scope
• there is no reaction
• non-professional influence
on the product
• draw attention from
the core feature implementation
Project Manager
it's an ideology
Agile will improve your development
within a short timespan
Agile means
better
or
worse
Agile is
than Waterfall
Agile = Scrum
Chain
What is the size of your project?
WF
for first stages
SCRUM's
a.berestovaya@mobidev.biz
How to use a hybrid?
Stable requirements; an identical app
must be built for another platform;
several extra features must be added
Project limitations:
• fixed budget
• specified deadline
Size: medium
Type of contract: fixed cost,
payment upon each milestone
Project type: growing startup
Input
Stack of practices
Waterfall as the main approach,
prepared delivery plan and deadlines for each stage
Fixed 1st iteration to clarify additional requirements, prepared Acceptance Criteria (RUP, Waterfall), detailed Risk Analysis (Spiral)
Prioritization of backlog, filtering features for MVP (RUP, SCRUM)
Kanban as the internal process: board, aim to speed up the development and avoid downtime, daily meetings (SCRUM).
Critical path as the criterion of task order
Code reviews for high-quality code delivery (XP)
Demo after each Milestone (SCRUM), delivery of the product according to the Acceptance Criteria
Results
• done within time and budget
• additional iteration for change requests
• managed to implement extra features
The project was finished successfully!
in addition to what was planned
• higher quality than that of the original app
• calm and stress-free atmosphere in the team
• happy Product Owners and End Users!
Individuals and interactions over Processes and tools,

Working software over Comprehensive documentation,

Customer collaboration over Contract negotiation,

Responding to change over Following a plan
Spiral
no planning
no documentation
"MobiDev team is a perfect technology partner for us, working really close to us and our product.

It was delivered in quality, budget and time.
The team even managed to hand over the final build for the launch weeks earlier than we planned."
held by product owners and teams
best practices
Full transcript