Scaling Agile across Distributed Multi-Vendored Environment
Many organizations are moving away from traditional style of software development. Though Agile practices are injected in the Enterprise after initial study , assessments and POC's, However, to reap the real benefits of Agile , it is important to have them successfully scaled across the distributed geographies and also have the whole organization transformed towards core agility. This is where the major bumps occur, as the organizations come out of their comfort zone and move towards a new world of Agility. It gets little more complex with multiple vendors and global distribution across different time-zones.
Me and Anand are working as Agile Coaches in a similar MNC Banking IT environment and would like to share our experience on How we are transitioning a huge traditional program towards better Agility , as Global Banks are leveraging Technology for enhanced Customer Experience to deliver Business value. They are moving away from transaction driven operations to enriched user experience and hence, there is a need of incorporating faster feedback, quick turn around and continuous value delivery to be ahead in the competition. This is where the need of core agility comes in place and its a mix of science , art and common sense. Our talk will take you through a journey.....
Outline/Structure of the Experience Report
Speakers Introduction 2 min
Base Foundation - Banking Organizations - 5 min
Agile Wave Challenges in Transformation - 10 min
People Factor - 10 mins
Best Practices - Tools & Technology - 5 mins
Agile Delivery Model - 5 min
Experience Sharing - 10 min
Q & A
- Agile Transformation in Huge Banking Enterprises
- Agile functioning in multi-vendor Environment
- Human Factor in Being Agile
- People Dynamics
- Organizational Boundaries in Agile Adoption and how to overcome them
- Collobaration Factors
- BDD,TDD, CI - Engineering Practices
- Merging Horizontal teams in cross-functional teams
Product Owners, Agile Practitioners, Coaches, Delivery Heads, Scrum Masters
schedule Submitted 5 years ago
People who liked this proposal, also liked:
Vishal Prasad - Agile Project Forecasting with Focus FactorVishal PrasadLead ConsultantThoughtWorks
schedule 5 years agoSold Out!
How many deliverables should we commit to our customers in, say, the next two weeks? An intriguing question asked by many Agile teams at the beginning of every iteration. The answer to this question depends largely on the team's thinking, philosophy, and skills -- which unfortunately cannot be measured. Then how do we forecast the deliverables?
How about a mathematical formula that provides an unbiased control based on the historical achievements of the team, which can be used for prediction? That's exactly what focus factor does.
Om Prakash Bang - Writing Excellent Requirements in agile wayOm Prakash BangAgile and BA coach, trainer and consultant.
schedule 5 years agoSold Out!
Traditionally Project Manager was playing a role of Business Analyst in a small and medium organizations. Leading organization have come to understand that Business Analyst as a separate role is critical for success of a project. As organizations are undergoing agile transformation and adoption, role of business analyst need to be redefined. What are the different options for Business Analyst in scrum; Partner with Product Owner? Transition to Product Owner? Part of Agile Team? What are the characteristics of agile BA? The core activities, skills remain same, but the way they perform differs.
This presentation is to give walkthrough on
- Role of Business Analyst in agile
- Progressive elaboration of Product Backlog Items / Feature / User Stories
- Requirement communication in agile
- Quality of Product Backlog Items / Features / User Stories
- Factors in writing excellent requirements
Why product backlog refinement is important for the success of agile project? How it improves productivity of team? What should be the writing style and how much level of details is good enough. The session also includes 30 - 45 Minutes of workshop on requirement elicitation.