Proposed (4)
Liked (37)
Commented (66)
Naresh Jain
Score 555
Naresh Jain

Tech-Startup Founder & Agile/Lean Expert

Agile FAQs

  India

Naresh Jain is an internationally recognized Technology & Process Expert. Over the last decade, he has helped many Fortune 500 companies like Google, Yahoo, Amazon, HP, Siemens Medical, GE Energy, Schlumberger, EMC, Alcatel Lucent, to name a few clients.

Naresh Jain's Startup Icons

Naresh is leading two tech-startups, which build tablet-based adaptive educational apps for kids, conference management softwaresocial-media search tool and a content curation and voting platform. His startups are trying to figure out the secret sauce for blending gamification and social learning using the latest gadgets.

As an independent consultant, Naresh worked with many fortune 500 software organizations and startups to deliver mission critical enterprise applications. Having played various roles of Founder, Agile Coach, Quality Evangelist, Technical Lead, Product Owner, Iteration Manager, Scrum Master, Developer, QA, Recruiter, Build Master, Mentor & Trainer, he is well equipped to help your entire organization to rapidly adapt Agile and Lean methods.

Agile Software Community of India

Naresh founded the Agile Software community of India, a registered non-profit society to evangelize Agile, Lean and other Light-weight Software Development methods in India. Naresh is responsible for conceptualizing, creating and organizing 50+ Software conferences worldwide.

Member since 11 months

Naresh Jain proposed:


Naresh Jain
Naresh Jain
SAMPLE PROPOSAL - Product Discovery Workshop
Naresh Jain
Naresh Jain

Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

This is a sample proposal to demonstrate how your proposal can look on this submission system.

Duration: 90 mins
Type:  Tutorial
Level: Beginner
» »
90_mins  
×
tutorial  
×
beginner  
×

product-owner  
×
agileux  
×
workshop  
×
11 months ago by Naresh Jain

Naresh Jain
Naresh Jain
Continuous Deployment for iOS Game Development
Naresh Jain
Naresh Jain

"Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

Our main question was: As mobile app developers, how should we architect/design our apps for CD?

We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

Duration: 45 mins
Level: Intermediate
11 months ago by Naresh Jain

Naresh Jain
Naresh Jain
Scaling XP Practices inside your organization using Train-the-Trainer Model
Naresh Jain
Naresh Jain

How do you effectively scale skill-based, quality training across your organization?

Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.

Duration: 90 mins
Type:  Workshop
Level: Advanced
11 months ago by Naresh Jain

Naresh Jain
Naresh Jain
Agile MythBusters
Naresh Jain
Naresh Jain

As the popularity of Agile methods have grown, so have the misconceptions or myths associated with Agile also grown. These myths get even more glorified when we talk about them in the offshore or distributed context. And to make matters worse, you can throw in a fixed-price contract spanner into the engine.

Worry not! In this fun-filled activity, we'll collect facts from the participants that they believe are true and then we'll declare them as confirmed or busted after an interactive (heated) discussion.

Duration: 45 mins
Type:  Workshop
Level: Advanced
5 months ago by Naresh Jain


Naresh Jain liked:


Prasanna Vaste
Prasanna Vaste
Should we stop using Story Points and Velocity?
Prasanna Vaste
Prasanna Vaste

On Agile projects we estimate user stories in order to allow team to

  1. 1. Track velocity
  2. 2. Decide scope for the Iteration
  3. 3. Help Prioritize stories
  4. 4. Help Release planning

But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

Duration: 20 mins
Level: Beginner
11 months ago by Prasanna Vaste

Bhasker Kode
Bhasker Kode
Writing and improving tail recursive functions
Bhasker Kode
Bhasker Kode

What is tail recursion?

Snippets from a few languages

Design choices around recursion

What kind of functions can be made tail-recursive? 

How do you profile such improvements?

 

 

Duration: 45 mins
Type:  Talk
Level: Beginner
» »
45_mins  
×
talk  
×
beginner  
×

recursion  
×
profiling  
×
1 month ago by Bhasker Kode

Roy Nuriel
Roy Nuriel
The Quality Assurance Journey - From Waterfall to Continuous Delivery
Roy Nuriel
Roy Nuriel

In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

In this session I will share how we made the shift, while focusing on the change in our quality process.

As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

Here are some of the dilemmas we faced:

-          What are the differences between "Dev Tester" and "QA Engineer"?

-          How can we measure quality in 2-week sprints?

-          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

-          When and how should load testing be performed?

-          Automated v. manual testing

-          What testing should be part of the CI process?

-          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

Duration: 45 mins
Type:  Case Study
Level: Intermediate
»
beyond-agile  
×
»
45_mins  
×
case-study  
×
intermediate  
×

qa  
×
11 months ago by Roy Nuriel

Neil Killick
Neil Killick
The Guessing Game - Alternatives to Agile Estimation
Neil Killick
Neil Killick

Agile promotes empiricism and change, yet many practitioners continue to scope out and estimate delivery times and costs for software products and projects.

Defenders of the art of estimation claim that we need to estimate software projects in order to answer common business and customer questions such as:

  • Should we go ahead with this project? (go/no-go)
  • How much will it cost? (bottom line)
  • When will it be done? (predictability)
  • Should we do project B instead of A? (prioritisation)

This session challenges participants to flip these questions on their heads and seek alternatives to estimation rituals. It covers the many risks inherent with an estimation culture and demonstrates real, practical alternatives, both at the portfolio and the sprint level.

Duration: 45 mins
Type:  Talk
Level: Intermediate
»
beyond-agile  
×
»
45_mins  
×
talk  
×
intermediate  
×

agile  
×
lean-startup  
×
lean  
×
scrum  
×
11 months ago by Neil Killick

Andrea Heck
Andrea Heck
Distributed Product Owner Team for an Agile Medical Development
Andrea Heck
Andrea Heck

We are developing medical imaging and workflow software in an agile way with development teams distributed to several countries. One of the major challenges is how to set up and communicate within the Product Owner team. There we have to deal with the distribution, e.g., have the Product Owner either onsite with her peers or with her Scrum team, travelling, or with proxy. We need people who are good in two different fields of knowledge: medical and software development. As a third issues, the environment of the customers may be different in different countries.

We have ramped up local Product Owners in different countries, have found local collaboration customers, and have developed a set of communication channels and workshops how to synchronize Product Owners in the team, share a common vision and backlog with their Scrum teams, and collaborate with customers locally and globally.

Duration: 45 mins
Type:  Case Study
Level: Advanced
» »
45_mins  
×
case-study  
×
advanced  
×

11 months ago by Andrea Heck

Venkat Subramaniam
Venkat Subramaniam
Haskell for Everyday Programmers
Venkat Subramaniam
Venkat Subramaniam

I learn different languages not to make use of them, but to program in my current languages in a better way. As we adapt functional style of programming in mainstream languages, like Java, C#, and C++, we can learn a great deal from a language that is touted as a purely functional language.

Haskell is statically typed, but not in a way like Java, C#, or C++. Its static typing does not get in the way of productivity. Haskell quietly does lazy evaluation and enforces functional purity for greater good. Everyday programmers, like your humble speaker, who predominantly code in mainstream languages, can greatly benefit from learning the idioms and style of this elegant language. The next time we sit down to crank out some code in just about any language, we can make use of some of those styles, within the confines of the languages, and move towards a better, functional style.

Duration: 90 mins
Type:  Talk
Level: Intermediate
» »
90_mins  
×
talk  
×
intermediate  
×

functional  
×
lazy  
×
static-typing  
×
haskell  
×
3 weeks ago by Venkat Subramaniam

Ellen Grove
Ellen Grove
Build Your Dreams: User Requirements Gathering with LEGO Serious Play
Ellen Grove
Ellen Grove

Let your hands be the search engine for your brain! LEGO® Serious Play® is a powerful thinking, communicating and problem solving technique that can help you and your team do serious work through structured play activities using a popular and playful 3D modeling toy. Through a facilitated process of building models that, storytelling and reflection, every person at the table is engaged and actively participating in the discussion, whether the topic is individual aspirations, team relationships, developing a new product or solving a wicked organizational problem. Everyone builds and everyone tells their story – all participants have equal opportunity to put their own points of view on the table, unlocking new perspectives and exposing the answers that are already in the room.  LEGO Serious Play has been used successfully for team-building and problem solving in a variety of organizations, from NASA to RBC to academic settings and public utilities.  

This presentation provides a hands-on introduction to LEGO Serious Play, so that you can experience firsthand how using LEGO to do real work unleashes creativity and enables meaningful conversations in a very short time. We will explore how to use this playful technique to collaboratively elicit information about user requirements and strategic design issues using the open source User Requirements with Lego methodology developed by a team at the University of Lugano, Switzerland.  This approach is particularly suited to Agile teams that want to get team members and stakeholders sharing their different perspectives on common goals in an open and light-weight manner.

Duration: 90 mins
Type:  Workshop
Level: Beginner
» »
90_mins  
×
workshop  
×
beginner  
×

requirements  
×
lego  
×
11 months ago by Ellen Grove

Victoria Schiffer
Victoria Schiffer
Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?
Victoria Schiffer
Victoria Schiffer

I love being around awesome people, who build great products customers desire. 
I love learning from and together with these amazing minds. 
I love creating the right environment for teams to flourish. 
I love change, and learning from new experiences. 
I love working in Agile environments.

How about you? 
I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.

The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.

In our everyday life doing Agile we already respect these aspects in many ways. 
But do we practice what we preach as best we can?

I'd like to challenge your current way of thinking about people and processes. 
I'd like to challenge you to focus on you, before you focus on others. 
I'd like to challenge your current way of reflecting. 
I'd like to inspire you to go different ways. 
I'd like to inspire you to inspire others.

In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
"You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.

And why not take it even further? Why not go "Beyond Agile"?!

Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.

Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.

In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.

Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!

Duration: 45 mins
Type:  Talk
Level: Beginner
»
beyond-agile  
×
»
45_mins  
×
talk  
×
beginner  
×

coaching  
×
learning  
×
inspire  
×
reflection  
×
10 months ago by Victoria Schiffer

Ashish Parkhi
Ashish Parkhi
Techniques to Speed Up your Build Pipeline for Faster Feedback.
Ashish Parkhi
Ashish Parkhi

I would like to share my experience and journey on how we brought down our Jenkins build pipeline time down from over 90 minutes to under 12 minutes. In the process, I would share specific techniques which helped and also some, which logically made sense, but actually did not help. If your team is trying to optimize their build times, then this session might give you some ideas on how to approach the problem.

Duration: 45 mins
Level: Intermediate
»
agile-tools  
×
»
45_mins  
×
intermediate  
×

jenkins  
×
build  
×
fast-feedback  
×
ssd  
×
1 day ago by Ashish Parkhi

Jason Yip
Jason Yip
Think Like an Agilist: Deliberate practice for Agile culture
Jason Yip
Jason Yip

If I say, culture is important to adopting Agile, most people will just agree without even thinking too much about it.  But what is meant by "culture"?  Why is it important?

Culture is not typical behaviour; it is not what we say we value (but don't actually do).  Culture is our basic assumptions of how things work.  Culture is the logic we use to think through and respond to any particular situation.

If you imagine a pyramid, Agile practice and any other visible behaviour is on the top, stated or written Agile values and principles are in the middle, fundamental assumptions (aka culture) is at the base.

My session is intended to expose people to the base of that pyramid.

If culture is assumptions, then to understand Agile culture, we need to understand the basic assumptions of Agile.  To do this, I have created an approach called "Think Like an Agilist" that both exposes how we think through an "Agile situation" and allows us to deliberately practice "Agile culture".

The general idea is that I won't just talk about Agile culture and values, what I'll call "culture theatre", but rather expose people, who nominally consider themselves part of the Agile culture, to their underlying thought processes and assumptions, given a relatively difficult scenario.  Those thought processes and assumptions are the essence of culture (reference Edgar H. Schein).  What is interesting is noting when the thought processes and assumptions are different which indicates that there is a different culture at play.  What I've noticed is that this difference is common between novice vs expert Agilists.

Note that it isn't even about analyzing vs doing it mechanically but more about exposing what assumptions are being used to respond.

NOTE: I will be updating the attached slides as when I created them, I was framing it more as "doctrine" rather than "culture", defined as fundamental assumptions"

Duration: 90 mins
Type:  Workshop
Level: Intermediate
» »
90_mins  
×
workshop  
×
intermediate  
×

11 months ago by Jason Yip


Naresh Jain commented:


Tejas Dinkar
Tejas Dinkar
Monads you already use (without knowing it)
Tejas Dinkar
Tejas Dinkar

Monads are a little bit like Quantum Physics: If you think you understand quantum mechanics, you don't understand quantum mechanics.

Monads are very useful for chaining computation together, in a simple way. The best explanation I've heard for them so far is that they are `programmable semicolons'.

In this session, I'll describe a few patterns that are solved by monads in some FP languages, and how you are already using them.

Some monads I plan to cover:

* Maybe Monad (being the easiest to explain)

* List monad, and how it is used to model non-determinism

* The state monad

* The IO monad

And maybe a few others

Duration: 20 mins
Type:  Talk
Level: Beginner
» »
20_mins  
×
talk  
×
beginner  
×

monads  
×
1 week ago by Tejas Dinkar

Aditya Godbole
Aditya Godbole
Learning (from) Haskell - An experience report
Aditya Godbole
Aditya Godbole

Functional programming as a programming style and discipline is useful even in languages which are not pure functional languages. By practising programming in a pure functional language like Haskell, programmers can drastically improve the quality of code when coding in other languages as well.

The talk is based on first hand experience of using Haskell in internal courses in our organisation to improve code quality.

This talk will cover Gofer (one of the earliest variants of Haskell) as a teaching tool, including the choice of the language, the features from Haskell that should (and shouldn't) be covered and the obstacles and benefits of the exercise.

 

Duration: 45 mins
Level: Beginner
» »
45_mins  
×
beginner  
×

haskell  
×
gofer  
×
teach  
×
1 month ago by Aditya Godbole

U S VINEESH
U S VINEESH
Agility lessons from Nature
U S VINEESH
U S VINEESH

Ants have existed close to more than a 100 million years now and they can be considered as one of the most flourishing beings on our earth. They have colonized almost every landmass and they thrive in most ecosystems.

Have you ever wondered what makes them so successful?

This success of theirs in so many environments has been attributed to their social organisation and their ability to modify habitats, tap resources, and defend themselves. Ants are one among the most agile creatures that we have seen till date.

This talk is about
- What makes ants so successful?
- What strategies they apply for them to be successful
- A few lessons that we could take back for ourselves in our teams and lives to being more agile.

Duration: 45 mins
Type:  Talk
Level: Intermediate
»
agile-tools  
×
»
45_mins  
×
talk  
×
intermediate  
×

4 weeks ago by U S VINEESH

Shirish Padalkar
Shirish Padalkar
Application Security - The Agile Way
Shirish Padalkar
Shirish Padalkar

Traditionally application security has involved upfront design and a big bang penetration test after development. This leads to the phenomenon of “bolt-on” security that translates into increased cost and complexity.

Drawing on our experience on real-world projects, we show how security can be baked-in on an agile project. Using case studies we demonstrate how security concerns are captured during project inceptions, how developers write secure code, security testing is automated and how configuration management can help achieve secure deployments. This talk introduces several new concepts like secure by design, secure design patterns and lightweight code reviews.

Duration: 45 mins
Type:  Talk
Level: Beginner
»
agile-tools  
×
»
45_mins  
×
talk  
×
beginner  
×

security  
×
testing  
×
2 weeks ago by Shirish Padalkar

Ravinder Singh
Ravinder Singh
Converting a requirement into executable tests – BDT
Ravinder Singh
Ravinder Singh

This session will brief about the gaps that generally exist between managment and technical team memebrs. Here we will focus on how we can use Behavior driven development to fill this gap and can involve non-technical persons also in the development phase.

This will brief about how all the stakeholders in the development process (whether technical or non-technical) can be brought on the same page by using Behavior Driven Development.

Duration: 45 mins
Level: Intermediate
»
agile-tools  
×
»
45_mins  
×
intermediate  
×

bdt  
×
bdd  
×
2 weeks ago by Ravinder Singh

Pankaj Kanchankar
Pankaj Kanchankar
Line Managers - an Endangered Species in Agile
Pankaj Kanchankar
Pankaj Kanchankar

The matrix organization of yore relied on maximizing returns on each skillset. This lead to having line managers and practice horizontals.
Engineering managers looking after developers and practice managers looking after the respective practices of BA, QA and PMO. This lead to having multiple lines of reporting for team member whilst on the project.
In Agile teams, focus is on the self organising teams of empowered employees working towards common success criteria (project success is team success). Not everyone can be a PO or a Scrum Master. So is the role of so called line managers or practice managers become redundant?
Whats their role in the agile teams?
How their role needs to transform

In this talk I will be addressing these questions. Bring out how some of their responsibilities are now taken up by the team or Product Owner or Scrum Master. I will also be suggesting how line managers can take this as an opportunity to morph into more meaningful roles that help the organization and teams. 


Duration: 45 mins
Type:  Talk
Level: Intermediate
» »
45_mins  
×
talk  
×
intermediate  
×

1 week ago by Pankaj Kanchankar

Sunil Mundra
Sunil Mundra
Getting A Partner To Adopt Agile
Sunil Mundra
Sunil Mundra

Due to the business benefits which accrue from Agile, clients are demanding their IT Departments/Partners to adopt Agile. It is quite common to find a situation where the client has adopted Agile, but its Partner/Vendor has not.

This talk is based on my consulting engagement with a client who had adopted Agile and their partner had not, and the client wanted the partner to Adopt Agile.

The talk will cover the challenges encountered in getting the partner to adopt Agile, especially given the wide difference in cultures of both orrganizations and also the organizations being located in different continents. The talk will also cover the learnings from this journey.

Duration: 45 mins
Type:  Case Study
Level: Intermediate
» »
45_mins  
×
case-study  
×
intermediate  
×

1 week ago by Sunil Mundra

Zaheerabbas Contractor
Zaheerabbas Contractor
Enterprise Agile Adoption: An Organizational Change Management Journey.
Zaheerabbas Contractor
Zaheerabbas Contractor

We represent the Agile Center of Excellence at our Organization and are chartered to drive the change management initiative to imbibe Agile adoption across the enterprise.

We plan to share our experience on the Organization Change Management initiative that we took up to drive Agility across the organization.  Our journey towards the derived vision and strategy to increase Agility in the system to thereby achieve:

  • Nimble simplified processes.
  • Ability to respond faster to change.
  • And most critical: delivering increased customer value.

This is a continuous improvement journey and we initiated:

  • Structured multilevel communications of CHANGE to the teams.
  • Learning + Unlearning:  Structured Training and Development plans (Behavioral and Technical).
  • Bringing in Gamification as a tool to get millennial team members to learn quicker.
  • Approach to move from “Pyramid” to “Hour Glass” structure to align with the flat team structure.
  • Pilot: Career Development Framework Aligned to Agile structure and roles.
    • Bringing in change of G&O to align with Agile delivery
    • Enabling Talent Fulfilment to align to the Agile roles and structure
  • Pilot: Performance change management- Holistic approach to drive appropriate behavior
  • Brining in systemic changes to ease Agile adoption
Duration: 45 mins
Level: Advanced

Anirudh Bhatnagar
Anirudh Bhatnagar
Continuous delivery in enterprise - devOps and other challenges
Anirudh Bhatnagar
Anirudh Bhatnagar

In this presentation we will discuss :

1.) What does continuos delivery mean in and enterprise organisation.

2.) Why do you need it? -Business value, Long term versus short term vision.

3.) Few scenrios explaining, what are the impediments that are faced while implementing continuous delivery.

     - Agile Mindset

    - Control and cultural differences.

    - Resistance to change

    - Silos, difference between departments, concept of devOps.

 This section will involve cases studies and real problems faced in the projects implementing Continuous Delivery.                 

4.)We will see how enterprise customers are different than the cool startups and small companies. Sometimes the whole problem statement which build the basis of implementation in one organisation is discarded completely in the other company. All these real project scnerios will be addressed.

Duration: 45 mins
Type:  Talk
Level: Beginner
2 weeks ago by Anirudh Bhatnagar

Sridharan Vembu
Sridharan Vembu
Distributed Agile for big Enterprises - Yes, it is possible!
Sridharan Vembu
Sridharan Vembu

The common myth about agile methodology is, it is suited for smaller, colocated teams, would not scale up for big enterprises and is best suited for smaller, less complex programs.

In this talk, I would like to share my views on how agile can probably be the right and best tool to solve most of the complex problems enterprise CXOs are facing and why their PMO/Project teams are not able to address majority of these problems through traditional execution approaches.

  

Duration: 45 mins
Type:  Talk
Level: Intermediate
» »
45_mins  
×
talk  
×
intermediate  
×

2 weeks ago by Sridharan Vembu