Agile Network India - Navi Mumbai Title: Agile project development -"A Journey" by Indulekha sing Date: 28th Jan 2024 Hosted by: Merce Technologies Pvt Ltd

1. Agile Project Development,
A Journey!

2. An interesting challenges in some projects
● Develop 2 mobile apps and publish for 12 apps (2*3*2) in
shorter timespan. (Android and iOS).
● Backend APIs were developed by client.
● New tech stack.
● Moving Baseline.
● Frequent implementation changes.
● Unstated features in SOW.
● No SRS documents.
● Multiple Communication channel.
● Single SPOC from our end vs Multiple SPOC from client’s end.

3. Proactive Approach

4. Proactive Approach - Prep before Project Kick-Off
● Learning and preparation phase started much before the
project started.
● Engineers having similar project experience were picked.
● Internal stand-up modules for the team are set much ahead of
time to build collaboration.
● Create and maintain a cross-functional team ahead of project
start.

5. Proactive Approach - Using tools effectively
● Establish scope before the Project starts.
● Eliminate false dependencies: Scheduling work in parallel, creating lagged
dependencies for the phase gate transitions.
● WBS: Define early based on SOW.
● Early sprint planning brings clarity of thoughts and goal for the entire
Team.
● Task priority brings clarity to tasks.
● Backlogs maintain better alignment.
● Clear Roadmap: Not just features but also Challenges + issues. Gives real-
time project insights.
● Team involvement in the entire planning approach - brings transparency,
clear approach.

6. Proactive Approach - Lateral approach
Standard approach
● Design UI Screens based on Figma.
● Expected list of all the APIs to be implemented.
● APIs request and response spec document.
● Communication between teams to understand and integration of API to screens.
Agile approach
● Asked for alternative. Client gave their web portal access for self understanding.
● Identity multiple hidden screens and reported to get the designs.
● Studied their web portal to understand the APIs and screen mapping.
● Studied their “source code” to understand the implementation and logics.

7. Proactive Approach - Development
● Work faster and more effectively in teams rather than silos.
● Start with imperfect product, iterating and improving quickly.
● Fast decision making and content iterations with daily and bi-
weekly meetings and collaboration platforms.
● Eliminate unnecessary meetings, events and travel, allowing
people to focus on what really matters.

8. Proactive Approach - Testing and documentation
● Common test cases started earlier based on the wireframes and
screen designs.
● Create a common checklist for production acceptance.
● Team had time to refine and refactor the test case for complex
modules.
● Functional documentation took off quickly.
● Reduce project gap by regular review and reflection calls between
dev and testing teams.

9. Proactive Approach - Deployment
● Parallel account setup for multiple environments for android, iOS
and web.
● Mobile app deployment has its own challenges with changing rules
and policies of google and apple accounts.
● Start with early deployment setup, avoid late surprises.
● Practice of CI/CD.
● Circulation of formal release note with the client on each
deployment.
● Key advantage - early identification of issues.

10. Baseline Clarity

11. Expected Baseline
Expected baseline we had discussed and agreed in SOW.
Shift in the Baseline
Actual baseline during implementation

12. Baseline Clarity
● Why did the baseline shift?
Parallelly development at client end.
Ambiguous requirement.
Continuous change in existing features.
● How was shift in baseline identified?
Agile development implementation.
Early testing helped to identify moving baseline.
● How did we resolve the issue ?
Prompt communication, documentation, daily call with customer on
baseline challenges.

13. Communication Model

14. Internal & Horizontal Communication
● Daily standup.
● Frequent catch-ups.
● Internal review and demo.
● Decentralized decision making.
● Weekly project updates to management.

15. External Communication
Go direct, using a combination of channels. Remove huddle, do not
stick to only one plan.
● Adopt multiple-client communication as per client’s need for fast
and easy communication. Like Slack, Jira, Teams, WA, etc.
● Bi-weekly communication with client team for progress update.
● Daily 15 minute to discuss baseline challenges call between 2
teams.
● Regular governance call to present overall project progress, risk,
issues and any challenges discussion.

16. Option Based Approach

17. Option based approach
Always table options to break status-quo
● Reduces the response time.
● Reduces multiple iterations in development cycle.
● Brings speed to development.
● Focus on the removal of any blocker and hard stop in agility.
Eg.
● Calendarization-based approach.
● Go for 2-3 option in UI screen design. Easier to derive to a decision.
● Provide technical support for blockers: Eg login module in mobile
app

18. Early Risk Identification

19. Early Risk Identification
A risk is an issue that is likely to happen.
● How to identify risk earlier ?
○ Create exhaustive risk checklists, review documents, analysis of
assumptions and constraints.
○ Experience and knowledge from previous projects.
● When and how to communicate Risk ?
○ The earlier the better. Long waiting also brings unexpected
surprises.
○ Weekly update, Governance call.
○ Add risk to the previous examples while communicating the cause
and effect.

20. Advantage for early Risk Identification
● Helps to keep project on track and avoid unwanted project delays.
● Creates a safe and secure work environment for all staff and
customers.
● Avoid the risk to convert into issues.

21. Summary for takeaways
● Proactive approach to keep the project on time delivery in entire
project phase.
● Baseline clarity to avoid late surprises.
● Effective communication model.
● Benefit of option based approach.
● Importance of early Risk identification.

22. Addition agile approach
● Pre-defined learning approach.
● Train around the tools and processes.
● Industry best practices.
● Know the values and culture.
● Assign a buddy.

23. Thank you