A brief summary of Agile Product Management, User stories, Vertical slicing, estimation Overview of TDD, SOLID principles

1. Introduction to Agile Software
Requirements
Abhilash Chandran
Development Manager
Xerox

2. What are we going to discuss
today?
• What stories are
• Writing User Story
• Estimation
• Workshop

3. Books …

4. Product Vision
• What the product should look like when
ultimately finished
– Type of features supported
– Type of users
– Market share etc.
• Continuous change because of
– New knowledge
– New customer base
– New or changing market conditions

5. Product Vision…
• Should contain
– Product features (as would be listed on the
product box or web site)
– Target market/customers
– Key differentiators

6. Cone of uncertainty

7. Continuous iterations
• Traveling at night
• Embrace the change
• Write only what you have
• Do only what you know
• Add new insights

8. User Roles
• A user role is any type of user that interacts
with the system
• Identifying the different types of Users is the
first step in Agile Product Management
• Lack of a clear understanding of User Roles
– critical requirements can be missed or
misunderstood
– Higher probability of developing a wrong software
with unwanted features .

9. User story
• A sentence or a paragraph that describes
functionality of the system from the user’s
perspective
As a <type of user>
I can <perform some task>
[so that I can <achieve some goal>]

10. User Story…
• As a user,
I want to reserve a hotel room
• As a frequent flyer,
I want to rebook a past trip
so that I save time booking trips I take often.

11. 3 C’s
• Card: The written description of the story
• Conversation: Verbal discussions that bring
out further details of the system
• Confirmation: the conditions of satisfaction
that are used to determine when the feature
is complete
– Should also include key conditions or constraints

12. Conversation
• As a user, I can cancel a reservation.
– Does the user get a full or partial refund?
– Is the refund to her credit card or is it site credit?
– How far ahead must the reservation be cancelled?
– Is that the same for all hotels?
– For all site visitors? Can frequent travellers cancel
later?
– Is a confirmation provided to the user?
– How?

13. Conditions of satisfaction
• As a user, I can cancel a reservation.
– Verify that a premium member can cancel the
same day without a fee.
– Verify that a non-premium member is charged
10% for a same-day cancellation.
– Verify that an email confirmation is sent.
– Verify that the hotel is notified of any cancellation

14. Split Stories
• As a user, I can cancel a reservation.
– As a premium site member,
I can cancel a reservation up to the last minute.
– As a site visitor, I am emailed a confirmation of
any cancelled reservation.

15. Epic
• A very large user story
• As a user, I can cancel a reservation.

16. Start with Epic
• MMF – Minimum Marketable Feature
• A basic set of features required for product
which can be marketed

17. Estimation
• Planning Poker
– It is about size not duration
– Identify the relative value

18. Activity
• User story breakdown
• Estimation

19. Part II
• Workshop on Clean code

20. Book…

21. Test Driven Development

22. Demo
• Demo with C# and MS Unit Test

23. Demo
• Demo with C# & Specflow

24. Behaviour-driven development

25. SOLID Principles
• Stands for five basic principles of object-
oriented programming and design
• Are guidelines that can be applied while
working on software to improve code quality
• Helps in
– low coupling,
– high cohesion
– strong encapsulation

26. SRP
• Single responsibility principle
A class should have only a single responsibility
(i.e. only one potential change in the software's
specification should be able to affect the
specification of the class)

27. OCP
• Open/closed principle
Software entities … should be open for
extension, but closed for modification

28. LSP
• Liskov substitution principle
Objects in a program should be replaceable with
instances of their subtypes without altering the
correctness of that program

29. ISP
• Interface segregation principle
Many client-specific interfaces are better than
one general-purpose interface.

30. DIP
• Dependency inversion principle
One should “Depend upon Abstractions. Do not
depend upon concretions.

31. Questions

32. Contact Me
• Email : c.abhilash@gmail.com
• Twitter : https://twitter.com/cabhilash
• Blog : http://www.TheAgileSchool.com