The document discusses the challenges and perspectives of a project called 'epicbite' undertaken by an agile team led by product owner Suzie and agile evangelist Angie. It highlights the tensions between agile principles and legacy approaches, the importance of communication, and the need for flexibility in requirements amid constant changes in the market. The text concludes by emphasizing that being truly agile requires openness to new ideas and methods, as well as building processes around motivated individuals.

1. Elevate
customer satisfaction with agile principles

2. Meet "Agile Alphas"
“The agile principles are our mantra!”
But have they truly stepped away from the legacy approach?

3. Introducing
the Product Owner,
Suzie
"I have all the requirements. All I need now is a
great agile team to make this new product a
super success!"
150++ 200+
Suzie is great at what she does. She believes in agility BUT, does the
process really allow her and the dev team to be agile?

4. Meet the
Agile Evangelist, Angie
"Agility is a mindset. How far has the team
actually come from the legacy approach and be
the agile team they claim to be? Let me help
figure this out"
Lets see how Angie can help them!

5. Project
"EpicBite"
The Agile Alphas are handed the
project with high expectations by Suzie.

6. Does a prefect requirement gathering
exists?
1
"This feature change
would be necessary to
stand out in the market.
If only I had access to the
developed features
earlier" - EpicBite
"But all that effort! With
this short deadline, we
cannot deliver on time
with the changes” - Agile
Alphas
3
2
"We have to accommodate
this change within the
same deadline" - Suzie

7. Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.

8. Welcome changing requirements, even late
in development. Agile processes harness
change for the customer's competitive
advantage.

9. The Anxiety
1
"When will I be able to
test the product to see if
it aligns with my product
vision?" - EpicBite
"The API is done but
integrations is remaining.
We also have feedback on
the completed tasks to be
incorporated" - Agile
Alphas
3
2
"I would need the updates
well documented in the
product roadmap" - Suzie

10. Deliver working software frequently, from a
a couple of weeks to a couple of months, with
a preference to the shorter timescale.

11. Business people and developers must work
together daily throughout the project.

12. The Debate: Supervise or Control?
1
"The team seems so
unenthusiastic about the
product with all the
missed deadlines" -
EpicBite
"I don't want to be
micromanaged! I need
space to be in my zone!" -
Agile Alphas
3
2
"I need daily updates!
Cannot afford more
extensions!" - Suzie

13. Build projects around motivated individuals.
Give them the environment and support they
need, and trust them to get the job done.

14. The Crunch Time
1
"So many bugs and UI
polishing is to be done.
This is not market ready"
- EpicBite
"So many edge cases were
not thought of by the
design team. We need
more time” - Agile Alphas
3
2
"We have to show
something to the client" -
Suzie

15. Working software is the primary measure of
progress.

16. The Confusion
1 "I will email the feedback
and details later" -
EpicBite
"I received a five pager
feedback document but
hardly anything makes
sense" - Agile Alphas
3
2
"I will just forward the
email of the requirements
change" - Suzie

17. The most efficient and effective method of
conveying information to and within a
development team is face-to-face
conversation.

18. Optimistic or over confidence?
1
The market is changing.
We need to prioritize the
requirements again" -
EpicBite
"We missed the last sprint
goals. We need to get
them done along with the
targets of this sprint and
the additional features" -
Agile Alphas
3
2
“We need to add more
features to the sprint
goals. The requirements
has changed" - Suzie

19. Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant
pace indefinitely.

20. What is the real definition of done?
1
"The app keeps loading in
every screen. Bad user
experience!" - EpicBite
"Refactoring and UI/UX
QA would be considered
later if there is time. Let's
wrap up the functionality
first!" - Agile Alphas
3
2
"The nonfunctional
requirements can be dealt
later as it is not mentioned
in the SOW" - Suzie

21. Continuous attention to technical excellence
and good design enhances agility.

22. Simplicity--the art of maximizing the
amount of work not done--is essential.

23. The Chaos
1
"There is a gap in what
was envisioned and what
is developed" - EpicBite
"It was developed as per
the product design. I
knew this would not
work!" - Agile Alphas
3
2
"All communication
should run by me first.
What if the team suggests
out of the SOW?" - Suzie

24. The best architectures, requirements, and
designs emerge from self-organizing teams.

25. At regular intervals, the team reflects on how
to become more effective, then tunes and
adjusts its behavior accordingly.

26. Progress
Tracker
Smooth execution Motivated team SUCCESS !
Well informed

27. Registered Product Owner, Scrum Master
& An Agile Enthusiast
Kshitiz Maskey
"In a world that is constantly
changing, there is no
one-size-fits-all solution. Being
agile means being open to new
ideas and approaches"