Send the link below via email or IMCopy
Present to your audienceStart 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
Don't Lose Your Head With Agile: Choosing The Right Approaches For A Software Project
Transcript of Don't Lose Your Head With Agile: Choosing The Right Approaches For A Software Project
...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
Delusions about Agile
What are people using?
The statistics for past 3 years
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,
Who are the end users of your system?
does your project have?
small (<1000 h)
What type of contract
do you have?
Time & Material
What kind of project do you have?
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
• complicates work with the backlog
• there is always someone else to blame
and active user involvement
• excessive change requests
My favorite ingredients
for effective project management
Just a little about freedom...
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
it's an ideology
Agile will improve your development
within a short timespan
Agile = Scrum
What is the size of your project?
for first stages
How to use a hybrid?
Stable requirements; an identical app
must be built for another platform;
several extra features must be added
• fixed budget
• specified deadline
Type of contract: fixed cost,
payment upon each milestone
Project type: growing startup
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
• 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
"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