Accepted (12)
Active (6)
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.

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.

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

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

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 critical challenges encountered in getting the partner to adopt Agile, especially given the wide difference in cultures of both organizations and also the organizations being located in different continents. The talk will also cover the key learnings from this journey.

Duration: 20 mins
Type:  Case Study
Level: Intermediate

Prafulla Girgaonkar
Prafulla Girgaonkar
eXtreme Programming for ETL and Data Analytics
Prafulla Girgaonkar
Prafulla Girgaonkar

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.

Duration: 45 mins
Level: Intermediate
» »
45_mins  
×
intermediate  
×

sas  
×
sas-language  
×
statistic  
×
etl  
×
analytics  
×
procedural  
×
ci  
×
testability  
×
2 weeks ago by Prafulla Girgaonkar

Alexey Ilyichev
Alexey Ilyichev
Skype goes agile: don't repeat our mistakes
Alexey Ilyichev
Alexey Ilyichev

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. 

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

moscow  
×
anti-patterns  
×
startup  
×
4 weeks ago by Alexey Ilyichev

Yilmaz Guleryuz
Yilmaz Guleryuz
Fibonacci Pairing: Learning through Collaboration
Yilmaz Guleryuz
Yilmaz Guleryuz

According to many researches, we learn the best when we experience it personally, and we comprehend when we teach to someone else.

So if you want to achieve ample understanding of a topic, you’ll need to follow these basic steps:

"Listen -> Observe -> Do -> Share"

 

Pair-programming is a well-known practice, and it has been introduced by one of the thought leaders of Agile world, Kent Beck. I respect any technique that encourages collaboration and interaction among teams, and gets teams to communicate better.

However, if you want to establish understanding of mastery or a skill-set, and increase the shared knowledge across your team members, then you need to re-think & apply new techniques.

In this talk, I’ll share about What-Why-How of "Fibonacci Pairing" technique, which is yet another discovery from practice.

The main goal of that technique is to establish understanding and improve collaboration, without overcrowding by artificial ways like lecturing.

Fibonacci Pairing is simple yet very effective technique that can improve team work. This technique should be regarded as a complementary way to improve team culture effectively.

We will elaborate with practical examples, real life experiences, and applicable ways onto different contexts.

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

4 weeks ago by Yilmaz Guleryuz

Dhaval Dalal
Dhaval Dalal
The Tao of Transformation
Dhaval Dalal
Dhaval Dalal

"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.

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

rituals  
×
practices  
×
principles  
×
values  
×
ideals  
×
2 weeks ago by Dhaval Dalal

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  
×
1 month ago by Shirish Padalkar

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

srinivas chillara
srinivas chillara
Architectural hiccups (and you really shouldn't bother with sprint-0)
srinivas chillara
srinivas chillara

While design changes can be made as we go, sprint on sprint, the poping up of architectural changes seems insurmountable. It is need not be so.

In this session, we provide a narrative of an online gaming product developed. This is a massively multi-player online game, for casual as well as professional players (with real sustantial money). Such a product needs to grapple with non-functional imperatives well beyond the run of the mill server-side software. As the project progressed new performance and security imperatives materialised.

How the  team made adjustments in face of changing non-functional (and some perculiar functional) imperatives is the focus of this talk.

Duration: 45 mins
Level: Intermediate
3 weeks ago by srinivas chillara

Anand Bagmar
Anand Bagmar
To Deploy or Not-to-Deploy - decide using TTA's Trend & Failure Analysis
Anand Bagmar
Anand Bagmar

The key objectives of organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!
In order for these organizations to to understand the quality / health of their products at a quick glance, typically a team of people scramble to collate and collect the information manually needed to get a sense of quality about the products they support. All this is done manually.


So in the fast moving environment, where CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury, how can teams take decisions if the product is ready to be deployed to the next environment or not?

Test Automation across all layers of the Test Pyramid is one of the first building blocks to ensure the team gets quick feedback into the health of the product-under-test.

The next set of questions are:
    •    How can you collate this information in a meaningful fashion to determine - yes, my code is ready to be promoted from one environment to the next?
    •    How can you know if the product is ready to go 'live'?
    •    What is the health of you product portfolio at any point in time?
    •    Can you identify patterns and do quick analysis of the test results to help in root-cause-analysis for issues that have happened over a period of time in making better decisions to better the quality of your product(s)?

The current set of tools are limited and fail to give the holistic picture of quality and health, across the life-cycle of the products.
The solution - TTA - Test Trend Analyzer

TTA is an open source product that becomes the source of information to give you real-time and visual insights into the health of the product portfolio using the Test Automation results, in form of Trends, Comparative Analysis, Failure Analysis and Functional Performance Benchmarking. This allows teams to take decisions on the product deployment to the next level using actual data points, instead of 'gut-feel' based decisions.

There are 2 sets of audience who will benefit from TTA:
1. Management - who want to know in real time what is the latest state of test execution trends across their product portfolios / projects. Also, they can use the data represented in the trend analysis views to make more informed decisions on which products / projects they need to focus more or less. Views like Test Pyramid View, Comparative Analysis help looking at results over a period of time, and using that as a data point to identify trends.

2. Team Members (developers / testers) - who want to do quick test failure analysis to get to the root cause analysis as quickly as possible. Some of the views - like Compare Runs, Failure Analysis, Test Execution Trend help the team on a day-to-day basis.

NOTE: TTA does not claim to give answers to the potential problems. It gives a visual representation of test execution results in different formats which allow team members / management to have more focussed conversations based on data points.

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

4 weeks ago by Anand Bagmar

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
1 month ago by Anirudh Bhatnagar

Vineet
Vineet
Cook your Product better : story map and no estimate is the new recipe
Vineet
Vineet

I'll share my experience on how we shipped products faster using story maps and how team's focus on smaller goals than estimates / numbers / complexities helped us achieve it. 

The session would give an insight on:

  • Aligning team with product vision 
  • Shiping features fast / faster 
  • Better product backlog management 
  • Delivering without estimation 

 

Some of our challenges / questions were:

  • Are we delivering value ? 
  • How do we know we have delivered enough for our customers ? 
  • What is our priority right now ? 
  • Do we have a bigger picture ? 
  • Aligning team with product vision
  • Is tracking numbers the right thing to do ? 
  • How fast should we ship ? What are the related challenges ? 

We solved these questions / challenges first by using story maps and then removed estimation. Story map gave a clearer picture of what's planned and what's in the next customer release. Other ideas helped us easily identify when to ship and what to ship (I'll discuss more about these in the session). 

Story map is a great way to collaboratively identify the features, prioritize them and create milestones. We used story maps as our card wall also. It was an interesting experience :) 

No estimate helps the team focus more on goals and less on numbers. It helps the team to think more about the customers and how would they use the product and less about velocity, charts and commitment. It changes team's perspective and team starts shipping a usuable product for customers. 

 

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

4 weeks ago by Vineet

Venkat Moncompu
Venkat Moncompu
Testing at the Speed of Trust: Agile Practices That Build Confidence in Software Quality
Venkat Moncompu
Venkat Moncompu

Faster time-to-market and shortening cycle times are the goals of any software development engagement. Test automation is often seen as the means to reduce time-to-market. Test automation is the bedrock of agile software delivery – faster feedback from testing. However, customers constantly challenge testing teams on the benefits realized from test automation. The return on investment (ROI) is often perceived as falling short of expectations due to ineffective articulation of benefits. This suggests a deeper problem that is often overlooked, one of fundamental distrust, which needs to be addressed effectively. Successful test automation strategies deliver value differently than conventional project metrics triad—cost, scope, and schedule—they supplement them in ways that require you to think laterally.
Risk and value are orthogonal, i.e. it requires a significant effort to bring congruity between these two outcomes expected from the test project management. For successful test automation engagements, realization of one of these outcomes cannot be expected to follow by the successful management of the other.
Establishment of trust is a necessary condition for the realization of these outcomes. Testing covers the risks, but often fails to articulate the delivered value. Addressing the trust deficit requires us to understand the values that stakeholders seek, but often overlooked. A better understanding of trust involves demonstration of two significant attributes – Competence and Credibility. Demonstration of these attributes results in Confidence. Confidence in a product, and therefore its value, increases as testing progresses. Value delivered incrementally and risk managed iteratively is the beneficiary of this orthogonality.


Key take-away
• Address the challenges that testing teams face through impact mapping, value-stream mapping, and Lean testing techniques to influence the outcomes.
• Put in context test optimization against cost of quality (CoQ), balancing testing against risks, and apply industry best practices to articulate the value of testing to build confidence and credibility.
• Help the testing teams and stakeholders to view testing, especially test automation, differently and eventually, to test at the speed of trust.

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

transfer  
×
collaboration  
×
1 month ago by Venkat Moncompu

Sachin Natu
Sachin Natu
Inverting Test Pyramid - A First Hand Experience Report
Sachin Natu
Sachin Natu

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.

Business Impact:

  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.

 

 

Duration: 45 mins
Level: Intermediate
» »
45_mins  
×
intermediate  
×

testing  
×
test-pyramid  
×
4 weeks ago by Sachin Natu

Shweta Sharma
Shweta Sharma
Creating Business Relevance With Lean and Agile Practices
Shweta Sharma
Shweta Sharma

Businesses are still struggling today to align their IT goals with their business ones. More often than not, IT projects are so focussed on budgets and timelines that they often miss the whole value proposition of the undertaking. 

It is important therefore that along with keeping an eye on the timeline and cost, IT partners with the business and create a product roadmap which meets the business needs. For this to happen, the backlog needs to be in conotnuous evolution and business stakeholders need to be questioned on their prioirties and often rigid requirements sets.

This is where agile and lean practices help: in getting working prototypes / products out at the earliest and failing fast if at they have to. 

The talk will seek to walk through some real life examples from self experience, of how some IT projects failed succeeded by keeping business relevance at the forefront of their priorities, the practices these projects followed and the kind of client / business enagegment they demanded and obtained.

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

  
×
3 days ago by Shweta Sharma

Ajay Avinash Solanki
Ajay Avinash Solanki
Agile Coaching - Giving and Receiving Feedback
Ajay Avinash Solanki
Ajay Avinash Solanki

Agile is based on crossfunctional and self organizing teams. Agile is based on the Plan, Do, Review and Adapt Feedback Loop. Feedback is the basis of Agile. Feedback can be amongst team members, between Scrum master and the team, Product owner and Scrum Master, Stakeholders and Product Owner and various combination of the same. We generally give a deficit based feedback. We point out to the short commings, mistakes, fix blames etc. This is a very emotionally chaged discussion which leads to a lose lose situation and a bad relationship. Contrary to this Giving feedback should be based on strengths. It is a planned approach which has to be rehearsed before hand. The main objective of giving the feedback is to find out solution instead of fixing the blame. Let us learn the techniques by which this can be made possible.

Duration: 90 mins
Type:  Workshop
Level: Advanced
»
beyond-agile  
×
»
90_mins  
×
workshop  
×
advanced  
×

agile  
×
  
×
1 month ago by Ajay Avinash Solanki