This document discusses software agility. It begins by explaining why software agility is needed, such as to quickly deliver valuable products and respond to customer needs. It then discusses how software agility can be achieved, including choosing an agile framework, focusing on deliverables and speed, and changing organizational culture. Finally, it defines software agility, discusses common agile frameworks and methodologies, provides tips for choosing the right framework, and notes some common myths about agility.

1. Agility
Zaid Shabbir
zaidshabbir@gmail.com
>
02/08/2022
WHY
HOW
WHAT
<

2. Agenda
• Why needs software agility.
• How achieve software agility.
• What is software agility.
• Agile Manifesto.
• Agile Principals.
• Frameworks and method to achieve software agility.
• Choose the right framework / model.
• Be Aware About Myths.
Software Agility

3. Why We Need Software
Agility ?
Software Agility 3

4. Why Needs Software Agility
• Deliver high quality valuable product and services quickly in a sustainable way.
• Respond quickly to customer and users need and sustain in competitive environment.
• To maximize customer satisfaction.
• Run fast to achieve set goals.
• Easily and quickly adapt the change.
• Better stakeholders' engagement.
• User focused development.
• Better control on project delivery.
• Deliver maximum value.
• …
• And off course to maximum profitability $$$.
Software Agility

5. How We Can Achieve
Software Agility ?
Software Agility 5

6. How Achieve Software Agility
Software Agility 6
• Through better stakeholder coordination.
• Quickly respond to change and deliver continuously.
• Chose the most suitable software agility framework/model for your team.
• Needs to focus on deliverable values and speed.
• Speedup quality deliveries through automation.
• Be aware of waterfall integration with Agile methods ?
• To change the organizational culture and mind set.
• Promote team (we) culture instead of individual (I).
• Avoid heavy loaded processes, needs to promote simple and lighter weight processes.
• Automate maximum we can.
• Needs to promote cross functional team culture with T-Shape skills.
• Move on left shift approach.

7. How Achieve Software Agility
Software Agility 7
• To change the organizational culture and mind set.
• …
• Building a sense of ownership, respect, openness and trust culture.
• Promote facilitation, inspection and adoption culture from top to bottom
• Avoid fear and blaming culture.
• Set clear business vision and goals so that all the stakeholders on same page and put
efforts on same direction.
• Don’t forget to identify company objectives and measure key results quantitatively.
• Continuously monitor objectives and key results and adapt the adjustments accordingly.
• Internal /external retrospective about where we stand on Agility.
• Agility is just not for software development ?
• Don’t forget to adapt Devops / MLOPS.

8. What Is Software Agility ?
Software Agility 8

9. Agile Manifesto
• Individual and interactions
• Working product
• Customer collaboration
• Responding to change
< over
< over
< over
< over
• Processes and Tools
• Comprehensive documentation
• Contract negotiations
• Follow the plan
Software Agility 9
What is Software Agility
• Agility isn’t a formula, a framework, nor a set of roles and rituals to follow. It’s a
timeless way of thinking and being that matures with practice and skill (Joshua
Kerievsky, CEO Industrial Logic, Agile Alliance, 2022 )

10. Software Agility 10
What is Software Agility …

11. Agile Frameworks and Methodologies
Software Agility 11

12. Choose the Right Agile
Framework / Model But
How ?
Software Agility 12

13. Choose the Right Agile Framework / Model …
• Scrum: Recommended when meet following criteria.
• 3-9 people's team. Incase of bigger team we can split into multiple.
• Requirement not changing on daily basis.
• Aprox 70-80% predictable sprint backlog.
• Deliverables are expected after fixed iteration.
• Fully functional team and all the project/product development decisions made within
team.
• Within sprint, team is fully empowered to make decisions.
• Estimate stories so that we predict deliverables on each iterations.
• Dedicated roles for product owner, scrum master.
• All the scrum events are mandatory.
• No Limit on in-progress task, its team decision how they burn the sprint backlog.
13
Software Agility

14. Choose the Right Agile Framework / Model
• Kanban: Recommend in following conditions.
• 1-10 people's team, bigger team needs to broken in small.
• Requirements change on approximately on daily basis.
• No timebox deliverable plan.
• Resources may not be available for team100%.
• Visualize the team progress on board.
• Wants more flexibility in team.
• Team is not fully functional and depend on external factors.
• Limit the in-progress Items.
• No fixed iteration.
• Most suitable for supporting activates( product support, infrastructure management
etc.).
• No story estimation.
14
Software Agility

15. Choose the Right Agile Framework / Model …
• Scrum-Ban: Recommended in following conditions.
• 3-9 people's team. Incase of bigger team we can split into multiple.
• Goals are broken in sprint iterations and after each fixed time box iteration deliverables expected.
• Execute scrum events (daily standup, sprint planning, sprint demo, sprint retrospective) but we
may adjust as per requirements.
• Requirements may or may not change on daily basis but aprox 50% of iteration backlog clear.
• Resources may or may not be available for team 100%.
• Wants more flexibility in team.
• Team may or may not fully functional.
• Visualize the team progress on board.
• May or may not estimate stories.
• With respect to rolls and responsibility wants more flexibility.
• Set maximum In-Progress tasks limit.
15
Software Agility

16. Choose the Right Agile Framework / Model
• Extreme Programming: Recommended in following conditions.
• 2-12+ people's team.
• No requirements define, decisions made on the fly.
• Wants more flexibility in team.
• Most suitable for short term projects up to 1 month.
• More capable to accommodate the changes frequently.
• Works better where core standards and practices defined.
• On-Site Customer. Customers fully engaged with team.
• Pair programming.
• No timebox activity.
• No Story estimation.
16
Software Agility

17. Be Aware About Myths
Software Agility 17

18. Be Aware About Myths
• Agility transformation completed within 6 months.
• Agility is new.
• We are agile because we are on scrum.
• We are agile because we are using Azure DevOps / Jira.
• Agility is for only software development.
• Agility is best practice for everyone and everywhere.
• No documentation required in Agile.
• Agile team has complete freedom to decide how they work.
• Agile is a sliver bullet for all your problems.
18
Software Agility

19. Thank you
Agility isn’t a formula, a framework, nor a
set of roles and rituals to follow. It’s a
timeless way of thinking and being that
matures with practice and skill (Joshua
Kerievsky, CEO Industrial Logic, Agile
Alliance, 2022 )
Zaid Shabbir
zaidshabbir@gmail.com