Becoming Agile : Get back to first principles first
Talks about partial successes with Agile implementations. We have become iterative for sure and there is a definite sense of cadence. But concept to cash lead times are still quite high. A sense of dogma has crept in the rituals, they happen, but there is little soul.Team members are still quite stressed out; We have avoided the famous waterfall death march for sure but it is still a very tiring and painful long march. Organisations doesn't feel that they have reaped all the benefits which were promised. There is just a handful of companies who seem to be living the values and are really nimble in the market place. What went wrong?
Our focus on people, value, flow and quality instead of process,tools, cost, schedule and scope, got the attention but did not get internalised by all. So while we are adopting “Agile” methods we have not become “agile” yet.
There is a need to get back to first principles. There is a need to explain knowledge workers on the ground “Why” the principles work. Leaders need to do more than just support the change, they need to know, behave and do the right things. Lastly people do need to learn and love their craft. Yes, it is about money but is it also about autonomy, mastery and purpose.
The session takes through key concepts around people, business value, product development flow and quality via fast feedback, and invokes people to understand and let their team understand the basic principles first to lay a strong foundation, before building an Agile enterprise on top of it. It is only then the “real transformation” happens and the products get in front of the end users faster.
Outline/Structure of the Talk
What went wrong?- What about people?
- What about value?
- What about flow?
- What about quality?
- Becoming Agile
The first 5 sections introduce common issues with Agile executions as per authors experience backed up by some research. While presenting the problem the sections also tends to indicate what we are potentially missing. Section 6 brings it all together and suggests one of the possible ways of addressing the situation, specially in the Indian SI and captives context.
Learning Outcome
As mentioned about the session takes through key concepts around people, business value, product development flow and quality via fast feedback, and invokes people to understand and let their team understand the basic principals first to lay a strong foundation, before building an Agile enterprise on top of it. It is only then the “real transformation” happens and the products get in front of the end users faster.
Once the foundation is set correct application of Scrum, Kanban, XP, SAFe becomes a lot more intuitive and easier.Specifically it touches key Lean and Agile concepts at breadth and how they can be applied practically across an enterprise to reap benefits.
While the content is generic and valid for all scenarios, author tries to focus on specific issues and possible remediations in Indian captives and SI organisations context.
Concepts touched upon and examples provided in slightly more details as below:
People
- Teams
- Motivation
- Agile Leadership
- Communication, collaboration & co-ordination
Value
- Understanding your customer
- Prioritisation
- Delivering value early and often
- Trade offs
Flow
- Requirements
- Optimising Flow
- Batch sizes
- Work in progress
Quality
- Fast feedback cycles
Target Audience
Agile Team Members, Leadership, Company Executives, Agile Practitioners, Product Owners, Entrepreneurs
Links
http://www.valueflowquality.com
schedule Submitted 7 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Om Prakash Bang - Agile Business Analyst and Product Backlog Management
45 Mins
Talk
Intermediate
Agile Product development with Scrum is based on completing a set of User Stories within a time-box called a sprint. Stories describing user functionality. Conversatin with customer is the means of elaborating requirement. looks simple, right?
Only User Stories are enough for product development? If not, what all other documents are necessary and how these are progressively elaborated?
What's required before agile team start sprinting? What are the challenges while transitioning from waterfall to agile related to product requirement?
What's the role of Business Analyst in agile? BA moving into an agile team, moving to Product Owner? Can Business Analyst and Product Owner co-exist?
-
-
keyboard_arrow_downSekhar Burra - The secret sauce of Self-Organization
45 Mins
Talk
Intermediate
In this session, we discuss about the few facilitation techniques that a servant leader need to have to promote self-organization.
We also focus on Evolution of an Agile team, the traits of an agile leader and various of pit falls that do not lead to self organization.
How do you really make a team being controlled by a manager to become self- coordinating team?
We also look at key behaviours that helps changes stick.
-
-
keyboard_arrow_downVineet Patni - Lean - Agile: The Eternal Siblings
Vineet PatniTransformational Coach, Trainer & Speaker | Enabling Agility | Building Great TeamsScale Up Private Limitedschedule 8 years ago
30 Mins
Talk
Intermediate
What came first - Lean or Agile? It's a chicken-and-egg question for many. And then, there are beliefs that these two are separated twins.
If you think that Lean software development and Agile are the same, think again!
There are both difference and similarities in the Lean and Agile principles and practices.
During this talk, we will discuss on how Agile and Lean are related or different. Or are they two different names of the same thing? how the principles of Lean and Agile can be leveraged in order to create complex software solutions at enterprise level.
-
Saket Bansal
Girdharee Saran
Atulya Krishna Mishra
Ankit Tuteja
Gaurav Rastogi
