• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Bengaluru

Agile Transformation - Experiences with matured products

Challenges addressed • Maintaining the committed deliveries with required quality during transformation • Maintenance and handling customer critical unplanned tasks • Revisiting well established processes, strategies and mindset • Handling mix of programs in agile and waterfall during transformation • Transitioning to feature teams • Testing in agile • Multisite development Challenges addressed partially • Potentially shippable increments • Estimation & release planning • Interworking with dependent programs who are not agile • Moving targets of deliveries from dependent programs • Waterfalls within sprint • Handling parallel versions of programs • Diminishing individual commitment & ownership • Transforming to self organized teams • Ineffective usage of best engineering practices • Gap in know-how transfer when team members move out of team (no single owner for the feature/component)
Tags:

Documentation - Path to Agility

Documentation professionals face many challenges in implementing agile into their day to day work. The documentation agile modus operendi derived from the R&D makes it difficult for the Writers - be that the need to unlearn the dependency on engineering documents, or to cater to multiple scrum teams simultaneously, or to be lean with fat legacy content in hand, to be visible in Product Backlog, no data on velocity, or even to handle document review in patches. These are some of the unheard concerns in most of the Agile discussions.

Continuous improvement through retrospectives

Agile software development focuses on small incremental functional implementations to software that add business value, and generate revenue to the customer as well as the parent organization. When working in small time intervals, there are often times lot of situations and events that conflict or come in the way of iteration/sprint goals. Teams and Scrum Masters/ Iteration Managers often are lost in the details, and it is easy to forget the big picture. It is here that good facilitation skills and retrospectives are very valuable. This session will try to give an overview of experiences of the presenter during his role as Enterprise Agile Coach in several large/ small organizations. This will be an interactive session where the focus is to address challenges in conducting retrospectives in multicultural, distributed teams. Present challenges, and ways to overcome some of them.

SCRUM turning Scum - Ignoring the 'False Negatives'

Agile has become mainstream from small communities to large organizations; thanks to SCRUM for the popularity. The mainstream SCRUM has setup a wrong precedence along the way in both the vendor and customer organizations due to incorrect notions and understanding of SCRUM. Often it is seen that both customers and vendor teams experience some success factors quickly; a happy feel good factor which only stagnates with no improvements sooner than later. Implementing SCRUM based on the false premise will only be detrimental in the long run as scaling certain practices will prove to be difficult and hard. Most quick success and feel good factors are ridden with ‘False Negatives’. It is very critical for SCRUM teams to be cognizant of these ‘False Negatives’ and steer away from stagnation if Value in Delivery is the key criteria.

Cumulative Flow diagrams - Your first step towards Lean

This talk will guide through the techniques of creating and analyzing Cumulative Flow Diagrams. We will touch upon the concepts of Value Stream Mapping, Story walls, bottlenecks, WIP and Cycle Time.
Tags:

Our journey from Scrum to Kanban via ScrumBan : A case study

Being an agile developer I believe in the path - "Explore, adopt, retrospect and innovate". And of course the last but not least step is "disseminate". We have been using Scrum + XP combination since some time. These two together made great couple and gave birth lot of wonders in our project. Every one were happy and enjoying until that day. The day when product owner doesn't have enough tasks to fill 2 weeks sprint. Towards end of the project, where we have very few features or functionalities and more of bugs or improvements which comes into process slowly. Sometimes developers were too busy even to check his facebook account (Most important thing ;)). Some times they are having too much time. Nothing to discuss in planning meeting. Not sure how to track and how to maintain them. Then we came to know about this Kanban and started adopting to it slowly. In this session I would like to share our experiences with community.

Agility in Indian Context

World inhibits many diverse cultures. Many of us face hurdles if we implement something defined by different culture. Simple copy-paste do not work. Similarly, Indian system/culture is different than other cultures and author would like to highlight that there might be a need to customize a bit to be agile. The topic ‘Agility in Indian Context’ focuses on implementation of agile methodologies in Indian IT industry. I think that Agile is growing in India but many practitioners are still struggling to get maximum benefits out of agile methodologies as Indian context and culture is different in many ways. Some of the unique features of Indian Industry are: Distributed development, Enormous Youth Power, Comparatively high attrition, Fixed price model etc. And there are many more which I would like to discuss during this talk and a way to handle these business constraints or opportunities in Indian context.
Tags:

10 must have tools for Distributed Agile Teams

Although Agile Manifesto says Individuals And Interactions over processes and tools, Distributed Agile Teams are faced with the challenge of needing tools to get their job done. This presentation looks at the top 10 list of tools agile teams need in the distributed context. This is a fun and quick presentation
Tags:

Architecture and Design Evolution

Many project teams believe that at least the basic architecture for a system has to be in place before any detailed design or implementation begins. But that is just so waterfall-ish. Creating an architecture without any verification and linkage to business requirements is a risk and potential waste. The desire to have an architecture in place before implementation begins is perhaps fueled by the belief that architectural decisions are hard to change later. In this presentation participants will learn from practical examples how a fairly complex architecture can evolve across Sprints through implementation of stories and their progressive refactoring.
Tags:

Agile Development: Essence, Decoration and Myths

Yet Another humble attempt to break the myths and bring back the essence of Agile
Tags:
Syndicate content