狠狠撸

狠狠撸Share a Scribd company logo
Agile Mindset not Framework
19thOct ‘2019
Understanding Agile
Agile s/w development comprises various approaches to s/w
development under which requirements & solutions evolve
through the collaborative effort of self-organising & cross
functional teams & their customer(s)/end user(s).
Traditional v/s Agile Approach
Fixed Scope Variable Approach
Plan Driven Value Driven
Complete Solutions Functional Modules
Derisk start strategy Derisk on-the-go strategy
get in touch!
Twitter @99_niravmehta
LinkedIn nirav-mehta-28051991
Email niravmehta2891@gmail.com
Coin Game
https://www.youtube.com/watch?v=fh4nkQnWL6I
Agile mindset not framework
Values
● Individual and Interactions OVER process and tools
● No Documentation instead proper code comments is what
needs to be done.
● Customer collaboration vs contract negotiation.
Ask as many questions as you can at the beginning.
● Respond to changes. Over the traditional plan.
Principles
How we can be best as a team
● BA and Dev work on daily basis
● Give tools & Support
● Face2Face Conversation
● Constant pace of delivery is must
● Simplicity
● Self Organised
Principles
How we can be best for end user
● End users need to be happy
● Shorter time frame
Adaptiveness within the team
● Welcome changes
● Good design enhances
● Regular feedback
Primary Goal
MVP
THANK YOU
Twitter @99_niravmehta

More Related Content

Agile mindset not framework

  • 1. Agile Mindset not Framework 19thOct ‘2019
  • 2. Understanding Agile Agile s/w development comprises various approaches to s/w development under which requirements & solutions evolve through the collaborative effort of self-organising & cross functional teams & their customer(s)/end user(s).
  • 3. Traditional v/s Agile Approach Fixed Scope Variable Approach Plan Driven Value Driven Complete Solutions Functional Modules Derisk start strategy Derisk on-the-go strategy
  • 4. get in touch! Twitter @99_niravmehta LinkedIn nirav-mehta-28051991 Email niravmehta2891@gmail.com
  • 7. Values ● Individual and Interactions OVER process and tools ● No Documentation instead proper code comments is what needs to be done. ● Customer collaboration vs contract negotiation. Ask as many questions as you can at the beginning. ● Respond to changes. Over the traditional plan.
  • 8. Principles How we can be best as a team ● BA and Dev work on daily basis ● Give tools & Support ● Face2Face Conversation ● Constant pace of delivery is must ● Simplicity ● Self Organised
  • 9. Principles How we can be best for end user ● End users need to be happy ● Shorter time frame Adaptiveness within the team ● Welcome changes ● Good design enhances ● Regular feedback