From Incremental & Iterative to Agile – What's the Right Process For Your Team? Maurizio Mancini
description
Transcript of From Incremental & Iterative to Agile – What's the Right Process For Your Team? Maurizio Mancini
#atlassian
NOTES:
• Your main title goes in the large blue
font.
• If you have a title that naturally splits
into a subtitle, use the smaller green
font for the subtitle. If not, delete the
subtitle
PHOTO
1. Place your photo at around the
same size as the example photo
2. (Keynote users:) Move your photo
onto the blue shape below Select both
photo and shape and then choose
“Mask with selected shape” from the
menu. Double click the photo to edit
the scale and crop position.
MAURIZIO MANCINI • DIRECTOR OF QA • YELLOW PAGES CANADA • #QAANDPROCESSGUY
From Incremental & Iterative to Agile What is the right process for your team?
Software Engineering People!Software Engineering is a State of Mind…
Software Engineering Tools!• Once you have figured out the level of software engineering maturity of your
team, then picking and using the right software engineering tools is vital!
• Don’t under estimate the importance of tool acceptance! • It can easily de-rail any process implementation…
Software Engineering Process!Your software development management tool must be able to handle all types of process…
A Little History
Incremental and Iterative Development (IID)
IID has roots in the Quality Labs of Walter Shewhart – Hawthorne Bell Factory in the 1920’s and 1930’s.
X-15
Project Mercury
Typical Example of an IID Release
Incremental and Iterative Development (IID)
• Plan for X weeks of Increments followed by at least 2 Iterations • Typical release is between 6 to 12 weeks
Increment 1
Increment 2
Increment 3
Feature Complete
Iteration 1
Iteration 2
Code Freeze
Iteration 3
Ship
• Increments do not go to production • Not all testing is completed within the increment • Last “golden” Iteration goes to production
What’s in a Word!
able to move quickly and easily
Agile Illusions and Expectations!
Agile actually requires a higher level of
Software Engineering maturity!
What’s the story with IID and Agile?
• Agile • 2 Week Sprints • Sprint Planning Meeting • Daily Scrums • All disciplines (Dev, QA, PO) involved
at the start
How are IID and Agile similar?
• IID • 2 Week Increments/Iterations • Iteration Planning Meeting • Daily Stand-Ups • All disciplines (Dev, QA, Product Manager,
BA) usually involved at the start
• Agile • Every Sprint is Production Ready
How do IID and Agile differ?
• IID • Final Iteration is Production Ready
How do IID and Agile differ?
• IID • Teams Not Co-Located • Resources are not dedicated • Feature List • Product Manager • Project Manager • Testing mostly Manual, some Automated
• Agile • Co-Located Team (Physical or Virtual) • Dedicated Resources (PO, Dev, QA) • Product, Release, and Sprint Backlogs • Product Owners • SCRUMmaster • Testing mostly Automated, some Manual
• Requirements and Features • Use Cases • Use of Spec and/or Confluence • JIRA for all software development work • Estimated Hours for Features • Demos of Increments • Release Lessons Learned
• User Stories • User Acceptance Criteria • No Spec à JIRA and Confluence • JIRA and JIRA Agile for all software development work • Poker Planning • Sprint Reviews • Sprint Retrospectives
Which Process is Right for your
Team?
It Depends…
Change is Hard!Processes
Indicators Structures
Company Objectives
Hard Factors
Soft Factors
Influence
Fear Cultural Norms
Beliefs
Relationships
Wishes
Envy
Habits
Privileges
Ethics
Power
One Step at a Time!
Ask yourself a few basic questions…
What does Resource Commitment look like?!
Or
What does your Office look like?!
Or
What does your Virtual Co-Located team look like?!
Or
What does your Product Backlog look like?!
Or
What about Testing?!
Or
What Roles does your Team have?!
Project Manager Or
SCRUMmaster
Product Manager/Business Analyst
Or
Product Owner
Which Process?!
If your organization looks more like the left
side
If your organization looks more like the right
side
I want to do Agile/Scrum – Now What?!• Get Buy-In from all major stakeholders, then get Buy-In of the Team
• Commit resources to the project and Co-Locate them (Physically or Virtually)
• Training and Coaching
• Team should fly solo with coaches oversight and active participation as needed for a couple of sprints
• Story Writing – It takes practice
• Follow All the Agile Principals – Don’t cut corners
• Get used to shipping Frequently - Industry average 1 in 4 sprints
Change in Roles!
QA
Project Managers
Developers
Business Analysts
ScrumMaster – Who to Choose?
Retrospective!
The dose makes the poison
Paracelsus – the founder of toxicology had the following saying…
Retrospective!• Pick an SDLC that fits your organizations realities today.
• Pick the right amount of process or it will be poisonous and lead to an EPIC failure!
Retrospective!Can everyone in your organization commit to meeting ALL of the principals as prescribed by the Agile Manifesto?
Training and Coaching are vital to the success of any process deployment.
Have committed resources to implement and follow-up on the roll out of any process.
Key Takeaways #atlassian
Have an amazing ScrumMaster!
When you have multiple teams, some may be IID and some may be Agile.
Key Takeaways #atlassian
That will make your company money!
Key Takeaways
Picking the right process and tools at the right time
delivering high quality
software
leads to a happy
collaborative team,
#atlassian
Thank you!
MAURIZIO MANCINI • DIRECTOR OF QA • YELLOW PAGES CANADA • #QAANDPROCESSGUY