The Tao of Transformation
"To know, is good. To live, is better. To be, that is perfect." - The Mother
During the Agile adoption, its a common complain that many team in many organizations get caught up in the ceremonies or mechanics of Agile and fail to understand/appreciate the true value and spirit of Agile. And because of this, the original intent of the Agile movement itself is lost. This is a serious issue!
This workshop will highlight, a well-proven approach to transformation (not adoption) and show the distinct steps in this journey that an individual or a collective goes through when learning anything new. Activities, serving as examples, in the workshop, will focus to show the journey - that is, how to begin with rituals, then gradually move to practices, arriving at principles and eventually internalizing the values. Witnessing this gradual process of transformation will help participants discover for themselves their current progression. We hope this will serve as a guiding light during their Agile journey.
Finally, we will leave the participants to ponder upon and discover for themselves their ideals in life and work as this is not only applicable to software development, but also to any discipline where humans are involved, including life itself.
Outline/structure of the Session
To help the participants understand the progression from rituals to values, we'll take 4 common XP/Scrum practices [TDD, Daily Stand-up, User Stories and Retrospective] and show the journey from rituals to practices to principles and finally to values for each of them.
This is a hands-on session, which means the participants will actually take part in this journey. (To hear, is good. To see, is great. But to experience, is priceless.)
- TDD's journey from rituals to values [15 mins]
- Demo of a very ritualistic way of doing TDD [3 mins]
- Participants help us to move away from the ritual and see the real TDD in practice [3 mins]
- Another demo of what TDD would look like, if we focused on the core principles behind TDD [3 mins]
- Finally a glimpse of what TDD would look like, if we focused on the core values behind TDD [3 mins]
- Recap of the journey and its importance
- Stand-up's journey from rituals to values [15 mins]
- Demo of a very ritualistic way of conducting stand-up [3 mins]
- Participants help us to move away from the ritual and see the actual stand-up practice [3 mins]
- Another demo of what a stand-up would look like, if we focused on the core principles behind the stand-up [3 mins]
- Finally a glimpse of what a stand-up would look like, if we focused on the core values behind the stand-up [3 mins]
- Recap of the journey and its importance
- Similar break-up for User Stories and Retrospective (15 mins each) [30 mins]
- Recap - Definition of rituals, practices, principles and values [10 mins]
- Finally define ideals and map them to values. [10 mins]
- Q & A [10 mins]
- A realization that transformation is a journey from rituals to values.
- Clear delineation between Rituals, Practices, Principles and Values.
- What are Ideals and how they map to values.
We hope that it would leave the participants inspired enough to introspect the values they live or ideals they manifest. We expect the participants to go back to work and reflect upon their journey from rituals to value in their work context and refine their approach.
Anyone interested in understanding the true meaning of Agile - Scrum Masters, Developers, Testers, Business Analyst, Product Owners, Agile Coaches, Managers , CxOs
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Inverting Test Pyramid - A First Hand Experience Report
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Techniques to Speed Up your Build Pipeline for Faster Feedback.
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.
Development Impact - For one of our build job, below graph shows how the number of builds in a day have increased over a period of time as the build time has reduced. Frequency of code check-in has increased; Wait time has reduced; failed test case faster to isolate and fix.
Business Impact - More builds leading to quicker feedback and faster story acceptance and less story spill over.
eXtreme Programming for ETL and Data Analytics
Over the last decade, eXtreme Programming practices like User Stories, Evolutionary Design, Test-Driven Development (TDD), Behavior Driven Developer (BDD), Refactoring, Continuous Integration and Automation have fundamentally changed software development processes and inherently how engineers work.
Having experienced various benefits from XP practices on our J2EE stack, our team started to apply these practices to extract, transform, and load (ETL) and Data Analytics side of our product. Unfortunately, there is very little guidance available in this context, esp. for the SAS Platform. Right from finding the unit testing framework to structuring the code to designing our modules and setting up a Continuous Integration builds, our team had to figure out everything, the hard way.
Join us to understand the challenges we faced during this process and how we resolved these challenges.
Skype goes agile: don't repeat our mistakesAlexey Ilyichev
schedule 2 years agoSold Out!
In 2011, I worked for Qik, a startup that got aqcuired by Skype. At that time Skype was in the middle of an agile transition. Аfter aquisition, Qik team was told to adopt the Agile process used by Skype. I worked with the team as an agile coach. After adopting Skype's "agile" process, our ability to deliver was brought down to almost zero. In this talk, I'll tell you the story as it happened, analyze the key problems that we faced and describe how we finally solved them. Come to this talk, if you want to avoid similar mistakes. If you are already through with your transition, I would be interested to know if you see any patterns.
Application Security - The Agile WayShirish Padalkar
schedule 2 years agoSold Out!
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.
The Art of SQL Database Refactoring
"We've tested this feature thoroughly and it worked really well. But for some weird reason, it's really slow in production today...must be a network issue...or may be the server is having a bad day..."
Do you often hear these kinds of comments in your development team? Let us guess, your application is very data-centric and churns big blocks of data on every user request. And under the hood, your application is most probably heavily dependent on long/complex queries with joins, temp-tables, case-statements, nested queries, etc.
These SQL queries probably started-out very simple. But as your requirements evolved, iteration after iterations, the queries also grew in complexity. And most often, even if you test-drove your newer stories, the performance of these complex queries is not evident until you run them in production.
Given that our requirements will evolve and so will our database, how do you deal with the above problems?
There are TWO essential parts to evolutionary database design:
- The art of refactoring your SQL queries.
- Figuring out the right balance of what processing is done in SQL on the DB sides and what is done on your service side in your App/Web Server.
Join us as we take a tour of how we refactored our complex, non-performant queries and overall DB without hurting our time-to-market.