1 of 17

Slide Notes

Are we ready for Agile software delivery as a community?

What do we need to do to salvage the situation?

This is not an Agile v/s Waterfall battle

Good Practices and Principles should be learnt and absorbed

Only those who keep practicing and improving their crafts add true value to the society
DownloadGo Live

Why your Agile Project will Fail; Software Dev Practices to Save it

Published on Nov 21, 2015

There is plenty of knowledge and information about the rituals and Product Ownership side of Agility but are your team members ready for it? What are the practices that can save your project from failure?

Here we question our preparedness for agile software delivery as a community and explore practices for ensuring quality and success

View Outline

MORE DECKS TO EXPLORE

PRESENTATION OUTLINE

1.

Why your Agile Project will Fail

Software Development Practices to Save it
Are we ready for Agile software delivery as a community?

What do we need to do to salvage the situation?

This is not an Agile v/s Waterfall battle

Good Practices and Principles should be learnt and absorbed

Only those who keep practicing and improving their crafts add true value to the society
Photo by Viktor Hertz
2.

About me

  • Creating software apps since 16 yo
  • Maintained un-documented legacy code in a variety of programming languages
  • Former core contributor to CA ERwin
  • Scrum Alliance certified CSP, CSD, CSM
  • Core contributor to Agile Chandigarh
  • Love traveling and discovering beauty
3.

Are you ready for delivering quality S/W with Agility?

Think Again
Photo by Stéfan
4.

Global Scrum Alliance Certification Numbers

Source: https://www.scrumalliance.org/community/certificant-directory.aspx
We have 1 PO, 1 SM and 7 (+-2) team members; Are the team members ready for agility?
What is CSD?
Is CSD only for developers?

5.

Have you been there?

  • Anxiety not knowing what all will break by that small change?
  • Will you be able to deliver on your promises?
  • Wondering if you have tested enough
  • Now it takes forever to ship out new features
Photo by Alyssa L. Miller
6.

Traditionally

Common sense driven development
Photo by Dietmar Temps
7.

Common sense says

  • You need to create software first before you can test it
  • Adding automation to the scope of work slows you down
  • Pair programming means half the productivity
  • Developers don't write tests
Photo by Walter Benson
8.

Quality Assurance / Quality Control

There's a difference and both are important
Quality Assurance is process oriented and focuses on defect prevention

Quality Control is product oriented and focuses on defect identification
Photo by USACE HQ
9.

Modern Practices

Tools and Techniques
Photo by robpurdie
10.

T/B/AT Driven Development

It's probably not what you think it is
Boss calling me at dinner time!
Photo by andrewrennie
11.

Exploratory Testing

Adds more value than pushing buttons
Photo by Martin LaBar
12.

Pair Programming

A tool for quality assurance
Photo by esti-
13.

Peer Code Review

As a part of source control process - lessons from Open Source
Photo by Daniel Kulinski
14.

Static Code Analysis Tools

  • JSLint
  • SonarQube
  • Rubocop
  • Brakeman
  • Many more...
Photo by Kaptain Kobold
15.

Continuous Integration

16.

Take Aways

  • Invest in preparing the team members for Agility - CSD certification is recommended
  • Differentiate QA from QC
  • Automation is your friend
Photo by Juliana Coutinho
17.

Vibhor Mahajan

https://in.linkedin.com/in/vibhormahajan
https://in.linkedin.com/in/vibhormahajan

https://github.com/vibhor86
Photo by Jon Ashcroft

Vibhor Mahajan