Enough articles and literature is now available on challenges faced by organization and people during Agile Transformation. One of the biggest challenge is peoples mindset. People do all work, agile transformation will demand org change from top to bottom. However, the question is does everyone is well equipped to handle this change. Emotional Intelligence one of the most important but highly ignored element in IT or software industry and so forth during such huge transformation.

 Having better understanding of Emotional Intelligence will help everyone in organization to tackle Agile transformation far better way than one doesn’t have knowledge and skills of Emotional Intelligence.

These are components of Emotional Intelligence, Self-Awareness, Self-Regulations, Motivation, Empathy and Social Skills. Research shows that one can work on improving emotional intelligence. This talk will provide guidance how to use Emotional Intelligence at work especially mapped in context of Agile Transformation.  

Its easier to discuss challenges to get the ideas from concept to cash. But there finer human behavioral

elements when we talk about innovation and this session tries to address fundamentals of how innovations starts.

This session is mainly about the myth that "Innovation starts with an idea"

As a enterprise coach we all need to go beyond team coaching to enterprise transformation process to bring end to end agility into the organization.Coaches are connected with various business lines while coaching.They can visualize and help organization to break the organizational silos.

To be effective, the action taken must alter the interrelationship of the parts or silos. Unless one alters the relationship between or among the parts, there is little hope for effective change.

Using the principles of systems thinking offer coaches to new ways of seeing and of interpreting what we see.

As an enterprise agile coach how we can apply systems thinking at our work context a journey with me.

Sharing my learning and observations with deploying systems thinking for scaling agility into the organization.

I have all my linked in post related to this theme.

Explaining about 'What and Why TDD ?'

How to do TDD?

Also TDD best practices and benefits.

Demonstration (Hands-on: For java people having laptops and other required tools)

Every product development essentially starts with requirements collection of what product should do and what user wants. However this becomes the most difficult part to focus on what and where to start the development from. For years, the product development requirements have become inundated with requirements templates and word documents. The traditional 100-500 page requirements document that was widely practiced a few years ago was having its own limitations.  The teams particularly started feeling difficult to consume and manage these large documents and deliver value incrementally.

With more and more organizations moving to agile, the product development teams started going for leaner structures that represent crisply what customer / user wants from the product.

The teams are have done away with multi-page requirements documents and have adopted backlog as a source of managing requirements. The backlogs also started helping teams to break the large product expectations into multiple layers of epics, features/enablers and user stories. 

But, at times, during this breakdown, there are chances of losing the big picture and prioritization and hence impacts the value delivered to customer as early as possible. Story mapping techniques, created by Jeff Patton is one of the most popular way to help carve out the MVP from the big picture that helps the organization to realize value at the earliest. 

Agile Coaching concept is relatively new to us, but coaching has been a part of our culture since 2000 years. This session is a attempt to open those hidden treasures and enhance our true coaching culture. This is an attempt to see and learn from those stories told to us by our parents, grandparents to help us understand Agile coaching and create a great future to self.

The paper will highlight about how distributed agile teams will be empowered and how they can adopt different agile practices as their maturity grows.

Is the scaling framework your organization is on helping you to Be Agile or pretend to be Agile? How about drafting one that stays true to Agile principles and helps with what your organization needs most while scaling?

While there are many frameworks available to scale Agile it is important to discern if these prescriptions address the real problems that an organization encounters while scaling up.  Does one size fits all? Is it worth adopting a framework and then retrofitting the organization into it or it is a better proposition to understand the dynamics of the organization, the existing challenges and business objectives first and then carve out a scaling approach, keeping Agile principles intact, that suits the organization's needs best.

This interactive workshop is about discovering the best approach to create your own scaling framework, one that is custom made to respond to your organization’s needs. 

TBD

To be added

There are situations that agile coach and scrum master face challenges after a certain number of iterations in maintaining team’s enthusiasm adhering to core values and principals of agile and creativity. Team and stakeholders start feeling a kind of monotony and cyclic repetition of activities that largely impacts on Self organization and Cross functionality.

Specific to agile, Design Thinking so far is seen as a way of taking care of WHAT part by means of better and precisely building product backlog in early phase of the project. However it is leant that Design thinking can be practiced successfully in the rest of agile life cycle to address said issues.

Application of systematic and wisely selected Design Thinking techniques or methods through out the agile project life cycle significantly enhances the purpose and help us in keeping the team’s pace, interest and stick to agile manifesto. Hence Design ‘Agile’ Thinking.

Its high time that we go beyond the conventional thinking and learning for Agile and propagate the real essences of Agile and its various techniques. It’s truly said that half knowledge is more dangerous than full knowledge. Currently organizations are tangled with the misconceptions of Agile which are carried by managements and its high time they we help them overcome these wrong facts and misconceptions

This session will focus on few of high flown myths like

1. Agile is a Fad
2. Agile is a Methodology or Philosophy?
3. Agile is solution to every problem
4. Agile is not disciplined
5. Agile says no documentation
6. Agile Says No Planning
7. Agile has lot of changes
8. Agile doesn’t support Architecture
9. Agile means Fixed Cost Project?
10. Agile Means : No Manager!!!

Scrum ceremonies, in most of organizations which are currently on path of Agile Transformation is a substitute for SDLC processes which were earlier followed. The need is to get them out of the cocoon, and provide them with wide variety of options that scrum masters can incorporate in the scrum ceremonies, making it more effective, interactive and fun to attend along with serving the main purpose of ceremonies.

I myself in my project have experimented with various styles of retrospective, collaborative team activities and innovative style of doing stand ups. The finding from these innovative ideas is a good take away for the scrum enthusiast.

The entire journey of how a team considering ceremonies as burden are not reaching before time to attend them and at the same time delivering beyond expectations. We not only took the amateur group of people and delivered the goals but we created a highly functional scrum team out of it.

The goal for coming years to make this team more mature and cross functional will also be shared.