This is Agile vision sharing presentation prepared by me some time ago, To share my viwes in terms of entry-level people having thoughts, agile misconceptions, and transformation challenges. Any suggestions feedback well appreciated. Thanks jitander kapil

1. Agile Vision
1
By Jitander Kapil
● 16 Years of QA and development
experience in IT/Software Industry.
● Senior QA/Agile Leader

2. Agenda
▪ Agile Challenges and Transitions
▪ Agile Basics and Roles
▪ Agile Umbrella and Process in Numbers
▪ Agile Motivations and Need

3. Agile Transitions And Challenges
▪ Agile is culture change and culture change takes time – lots of time. To move to Agile is simple but implementation NOT: Stop
doing projects?
▪ Don’t fall into the trap of using certain approach “just because everyone else is”
▪ A transition to a mix of Agile and Waterfall methods is even more complex and need deeper level of executive support,
understanding, and tolerance.
▪ Quality itself was challenge and in Agile? will it be centralized or decentralized, Production hot fixes,Autmoation etc.
▪ Once adopted don’t compare methodologies e.g. Waterfal,Traditional Vs Agile? just review, Inspect and Adapt
▪ Being Transparent : Should be open about failures as well as successes.
▪ Make the changes gradually over time and give everyone time to adapt to them.
▪ Agile ≠ Scrum (Agile is a mindset, Scrum & Kanban are Agile methods)
▪ Agile is different it requires a conscious effort to embrace change. Please Don’t Try to modify it ---Trust it and let it
run:

4. 4
Model/Features Waterfall Model Agile Model
Requirement Specifications
Over All Process
Beginning
Heavyweight
Frequently changed
Lightweight
Understanding
Requirements Well Understood Well Understood
Simplicity Simple Not so easy
Documentation Vital Yes but as per need
Training required Vital Yes
Project Time frame Long Least Possible
Flexibility Rigid Highly Flexible
User Interaction Only at beginning High
Risk Involvement High Reduced
Risk Analysis Only at beginning Yes
Cost Low Initially High
Guarantee of Success Low Very High
Resource Control Yes No
Time Frame Long Least possible
Reusability Sometimes Limited Reusable
Changes Incorporated Difficult Adaptable
Important Facts Agile Waterfall
Architecture Informal and incremental Very well documented &finalized before coding
Team
Developers work as Team and share possession of the
code Each developer is responsible for one area.
CI Continuous integration Integration executed at one end or after milestone
Completion Focus
Focus is on completing stories (functionalities) in short
iterations Focus is on completing modules ( parts of the architecture) at large milestones
Engineering practices
Relies on engineering practices (TDD, refactoring design
patterns…) Doesn’t necessarily rely on engineering practices
Communication
Open door policy. Everyone's point of
view is considered.
Limited access to Business people. Communication happens mainly at the
beginning of the project & at the signposts.
● Waterfall isn’t “good” or “bad,” it’s just a certain way of doing things. Like any tool, it has its strengths and weaknesses.
● Greatest challenge moving from Waterfall to Agile is the team’s mindset. That need team’s approach to work.
● Make sure and Trust the project delivery approach you take and review Statistics ,like below, before start:
Agile Transitions and Challenges

5. Agile Basics and Roles:
▪ Agile is software development Method that has some key features: It has Values, Principles, and Methodologies.
▪ 1. Agile Manifesto (Values): The 4 Agile Values(Individuals and Interactions, Working software, Customer
collaboration and Responding to change) serve as the foundation of Agile philosophy.
▪ 2. Agile Principles: The 12 Agile Principles embody the Values and Provide more concrete examples of what Agile
means at a lower level.
▪ 3. Agile Methodologies: Methods that support Agile values and principles (Scrum, XP , …etc).
▪ Scrum Master
▪ Animate, organize, facilitate …
▪ One team only, Part of the team also
▪ Product Owner
▪ Define the vision, maintain the backlog
▪ Express stories so that the team knows what to do
▪ Team
▪ Autonomous, Multi-expertise & self organized
▪ No chain of command and decision maker

6. 6
Agile Umbrella:
● Agile is concept. All Agile development methods have shared philosophy and set of principles.
That need team’s approach to work.
● The Agile umbrella has many offerings depending on your needs.

7. 7
▪ Release length: 3, 6 or 1 year (i.e. adaptable)
▪ Sprint length: 2 weeks
▪ Team size: 7 including PO, SM, Architect and team members (DEV,DOC,QA)
▪ Story Complexity (1-377) based on Fibonacci series (377 = we don’t know)
▪ Sprint size about 250 points or 3 to 4 stories
▪ Any task complexity equivalent (<= 1 day), no hour management
▪ Stand-up or Scrum Of Scrum: 15 minutes
▪ Review done by the PO on a stable demo platform (30 minutes max)
▪ Sprint planning: half to 1 day including the task breakdown
▪ Sprint Retrospective: 2 hours
▪ Release planning: about 1 day
Agile Process in Numbers:

8. 8
▪ Diverse groups of like-minded (The right mindset makes practices more effective and work
better)
▪ Estimates ≠ Deadlines
▪ Release planning: about 1 day
▪ Release? Now At least better than previous Guess +Release
▪ PO/BA/Customer engaged from start of project deciding what gets built
▪ Team Management its own work. Now Managers don’t decide who does what?
▪ Dependencies Removed i.e. Cross functional Teams
▪ Promote high degree of collaboration
▪ Limit work in progress. Time boxed Iterations(Result in iteration 1-4 week)
▪ Work not just to finish, make it “Production Ready”
▪ Faster Feed back cycle Retros,SoS,SRs
▪ Over all Quality is known and Tests are fully automated
▪ There is only one Team and quality is it’s primary concern
Practical Motivations:

9. 9
Key agile Technical Concepts:
▪ Quality and Testing: BDD/TDD/Junit/IT/CI/CD
▪ Source Control Management : Perforce
▪ Build process : Maven
▪ Continuous Integration : Jenkins
▪ Quality Monitoring: SonarQube
▪ Component Repository : GIT,Nexus
▪ Workstation Environment : Eclipse,Intellije
▪ Testing Tools like Selenium, Rest assured ,Jmeter,scripting
▪ DevOps tools and concepts like Docker,contenrization,Salt,K8s etc.
▪ Repository and Standard Directory Layout
▪ Artifacts and Build Life Cycle
▪ The POM and Dependencies
▪ Versioning, Plugins etc.

10. Thank You
10