Pre-Conf Workshop Day 1

Sun, Mar 5
Timezone: Asia/Kolkata (IST)
09:30

    Registration - 30 mins

10:00

Pre-Conference Workshop Day 2

Mon, Mar 6
Timezone: Asia/Kolkata (IST)
09:30

    Registration - 30 mins

10:00
  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little / Kent McDonald / Niel Nickolaisen - Agile Leadership: Accelerating Business Agility

    schedule  10:00 AM - 06:00 PM place Jacaranda people 3 Interested add_circle_outline Notify star_halfRate

    Leaders today face constant, accelerating change driven by technology and incredibly high expectations from both internal and external customers. Surviving and thriving in this environment requires IT leaders who can reliably deliver the following:

    • Innovation that drives the organization forward
    • Innovation centered on creating competitive advantage
    • Results in the face of dramatic change and ambiguity
    • Excellence in delivery
    • A culture of motivation and agility
    • Relationships of trust both inside and outside of the organization

    In short, as IT leaders we need to transform our roles and our departments. But, what can we use to pull off this transformation? In this workshop, we focus on, teach and practice the tools of transformational leadership.

    Part one of the training dives deep into the Purpose Alignment and Business Value Models. These tools are proven and can be put to use immediately. Part two of the training covers tools leaders use to re-define their roles using the Trust / Ownership Model including agile principles.

    All of these tools are concrete, pragmatic, and usable. After each part of the training, participants are ready to use the tools to re-define their roles and deliver what their organizations need – brilliant leadership.

  • schedule  10:00 AM - 06:00 PM place Mangolia people 34 Interested add_circle_outline Notify star_halfRate

    Disciplined Agile (DA) is an IT process decision framework for delivering sophisticated agile solutions in the enterprise. It builds on the existing proven practices from agile methods such as Scrum, Extreme Programming (XP), Lean software development, Unified Process, and Agile Modeling to include other aspects necessary for success in the enterprise. DA fills in the gaps left by mainstream methods by providing guidance on how to effectively plan and kickstart complex projects as well as how to apply a full lifecycle approach, with lightweight milestones, effective metrics, and agile governance.

    The one-day workshop is not technical and is suitable for all team members. Many group exercises reinforce the principles learned. The workshop is also valuable for management tasked with moving from traditional approaches to agile.

  • Added to My Schedule
    keyboard_arrow_down
    Andrew Kaufteil

    Andrew Kaufteil / Nate Clinton - Leading Creative Ideation

    schedule  10:00 AM - 06:00 PM place Wills Lounge people 32 Interested add_circle_outline Notify star_halfRate

    Crack your head open and release a surge of creative ideas with engaging activities that promote clarity, inspiration, and buzz within your organization. We’ll cover methods and facilitation tools to ensure you run fruitful brainstorming sessions, leading your team to more and better ideas. You’ll learn to frame the problem you’re solving, come up with an exploration strategy, and facilitate the session, giving you and your team new ways to get inspired and energized when looking for solutions.

  • Added to My Schedule
    keyboard_arrow_down
    Julian Harty

    Julian Harty - Analytics Driven Software Engineering for Mobile Apps

    schedule  10:00 AM - 06:00 PM place Cassia people 9 Interested add_circle_outline Notify star_halfRate

    There's little need to work in a vacuum as an isolated developer or team. Our software tools, our apps, and our users all provide information we can use to help us improve our practices and the apps we produce. Some tools provide leading information - that's available and can be applied before we release the app. Other information lags the release of our app to testers and users, we receive the information as the app is being used. 

    The information may help us reflect on our existing work, what went well and what we missed or didn't do quite as well as we'd like to do. We can also use it to improve how we work in future, for instance to test more effectively and efficiently, to learn from production and real world use of our software, etc. We can choose to work faster, increase the value of the feedback we receive, and shorten the feedback cycles so we can iterate faster and more purposefully.

    In this interactive workshop we will be able to investigate and review some of the many and varied tools and sources of information. We will compare information that is easily available with techniques such as implementing and applying mobile analytics and designing automated tests to help us collect high-value, relevant information explicitly. We’ll also investigate the capabilities and tools that are available to developers and those who support mobile apps to harness these tools and the data they provide to refine and improve our testing. We'll also consider automated testing, their sweet-spots and their blindspots.

    In addition to general mobile testing techniques we’ll investigate ways to help decide what to test next and what might survive in the morass of “won’t be tested”. As we learn more about specific aspects of an app, we can further refine the testing and use various analytics and research to improve our testing. There’s plenty of data available to help us improve the testing and even the development of mobile apps if we choose to collect and use it. Privacy and protection of the users is also key and part of being a trustworthy, professional tester so we’ll touch on these topics and how they’re generally designed and implemented in mobile apps.

  • schedule  10:00 AM - 06:00 PM place Plumeria people 33 Interested add_circle_outline Notify star_halfRate

    Code that is difficult to understand, hard to modify and challenging to extend is hazardous to developers, users and organizations. Refactoring, or improving the design of existing code, is one of our greatest defenses against such code. Yet many programmers lack formal training in refactoring. Furthermore, management tends to lack knowledge about the value of refactoring. This one-day workshop is designed to address these needs. You’ll learn the art of refactoring safely, when, why and how to refactor hazardous code, strategies and tactics for refactoring, as well as refactoring to patterns. You’ll also learn how refactoring impacts business concerns and vice-versa. Come to this class prepared to code with a pair and a mob as we refactor example code and help you learn the art of refactoring.

18:00

    Invite ONLY Speaker Conclave - 240 mins

Agile Mindset

Tue, Mar 7
Timezone: Asia/Kolkata (IST)
08:30

    Registration - 30 mins

09:00
10:00

    Welcome Note - 15 mins

10:15

    Coffee Break - 15 mins

10:30
11:30
  • schedule  11:30 AM - 12:15 PM place Mysore Hall 1 people 39 Interested star_halfRate

    Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.

    It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.

    Effectiveness may just be the better target.

    Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:

    • Build a shared understanding of the problem you are trying to solve
    • Establish clear guard rails for distributed decision making
    • Measure progress based on outcome, not output

    Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.

    You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.

  • Added to My Schedule
    keyboard_arrow_down
    Zeger Van Hese

    Zeger Van Hese - The Power of Doubt - Becoming a Software Skeptic

    schedule  11:30 AM - 12:15 PM place Mysore Hall 2 people 14 Interested star_halfRate
    "I don’t know".
     
    These might just be the hardest words to say in any language. We avoid saying them, scared of coming across as doubtful and uncertain. This fear is understandable; we admire those who are knowledgeable and oozing with confidence - even more so in a professional context.
    As testers, our team members and managers expect us to be firm and certain, providing clear answers. They want us to hand them that comforting blanket of certainty. Over the past years, I grew increasingly uncomfortable with that. I ended up having a hard time being sure of anything, to the extent that my confidence as a tester started suffering.
     
    "You're rejecting certainty, just like Socrates", someone said. "That's skepticism. You're a tester, embrace it!". That sounded like a good way to get out of my little Socratic crisis, but it left me with a new challenge: how does one embrace skepticism, and how can this help me improve my testing? I wanted to get to the bottom of this and, for a year, decided to submerge myself in all things skeptic in hope of finding clues to help me with my testing and my struggles with doubt. It was a fascinating journey that brought me to both sides of the spectrum, ranging from hilosophy, religion, critical thinking to science and even pseudo-science. The latter proved to be a portal into the world of the odd, the awkward and the downright bizarre.
     
    Now that I surfaced safely, it is time to reflect and make sense of what happened. I will tell the story of how I embraced skepticism and be came a proud and reasonable doubter. I will share how this influenced my testing and how I harnessed the power of doubt: by creating a portfolio of critical thinking heuristics that can be valuable addition to any human's toolbox.
12:05
12:30
  • Added to My Schedule
    keyboard_arrow_down
    Gautam Rege

    Gautam Rege - Rewarding Open source with $$$

    schedule  12:30 - 12:50 PM place Mysore Hall 1 people 7 Interested star_halfRate

    What keeps Open Source contributors going?
    How do they get paid? In kind or in cash?
    Why doesn't everyone contribute? 
    Common questions, frequently discussed but the problem has not been solved. 

    Well almost! "CodeCuriosity" is a platform that measures your open-source contribution and rewards you for your effort! 

    What can be measured can be improved! CodeCuriosity helps you set goals for open-source contribution and scores it. The accrued score can be redeemed for merchandise from Github and Amazon!

    CodeCuriosity aims to be the Fitbit™ for Open Source Contributions.

  • Added to My Schedule
    keyboard_arrow_down
    Vishweshwar Hegde

    Vishweshwar Hegde - Mindfulness: Cultivating Agile Minds

    schedule  12:30 - 12:50 PM place Mysore Hall 2 people 26 Interested star_halfRate

    Agility starts with Mind. It’s about open, curious, energetic mind constantly looking for doing better things and in better ways. Such Agile Minds manifest in proactively sensing market/customer opportunities/needs early, quickly adopting to changes  to create new value in the changing contexts, continuously learning, exploring & experimenting new things. It requires courage, self-drive and taking people along. If we notice, all these characteristics are distilled in Agile Values & Principles.

    But how to develop Agile Minds? Typically our education system and corporate trainings  are predominantly IQ oriented; whereas Agile Mind is about Emotional Intelligence (EQ) – self awareness, self regulation, self motivation and empathy. EQ is an essential ingredient for a culture of self-organizing, collaboration and servant leadership – which are the tenets of good Agile culture. Mindfulness is a practical & effective toolset to cultivate EQ and create Agile Minds. 

    Being a Mindfulness practitioner, this talk will cover my experiences of consulting & coaching on Mindfulness in organizations driving Enterprise Agility.

  • Added to My Schedule
    keyboard_arrow_down
    Prabhakar Karve

    Prabhakar Karve - Importance of preparation in an agile world

    schedule  12:30 - 12:50 PM place Mysore Hall 3 people 19 Interested star_halfRate

    Significant improvements to our prepared for dealing with uncertainty in life and work can only happen when our repetitive patterns of behavior change permanently. Day-to-day occurrences around us offer a rich source of such improvement opportunities.

    All that is missing is a systematic way to look at our actions, interactions, decisions, emotions, and opinions as they are unfolding. The way of working (WoW for short) framework provides the missing link to fill this gap. It looks at what why and how of our ways of working. It also provides a step by step practice to make it a habit till it becomes our second nature.

    WoW framework is completely neutral – like air or water around us. It especially works well with agile by complementing it. Regularly practicing the new way of looking at things helps us to move from a fixed to an agile mindset.

    With the WoW approach we keep watching our actions, interactions, and emotions and link them back to our opinions and decisions. We will start seeing a permanent change for the better, only when we are able to correctly change our current decisions as well as transform our opinions.

12:50

    Lunch Break - 55 mins

13:45
14:45
15:20
15:30

    Coffee Break - 15 mins

15:45
  • Added to My Schedule
    keyboard_arrow_down
    Woody Zuill

    Woody Zuill - Mob Programming: A Whole Team Approach

    schedule  03:45 - 04:30 PM place Mysore Hall 1 people 33 Interested star_halfRate

    Mob Programming is a development practice where the whole team works on the same thing, at the same time, in the same space, and on the same computer. It is a whole-team approach to doing all the work the team does including designing, coding, testing, and working with the customers, users and other stakeholders. This is an evolutionary step beyond pair programming and accentuates face-to-face communication, team alignment, collaboration, and self-organizing team concepts of the Agile approach to software development.

    Mob Programming can be a highly effective approach to software development. There are numerous teams doing Mob Programming all over the world, including distributed teams, and there has been a great deal of positive reports of success. Please join me as I share how the concept got started, the benefits, techniques we use, and some of the problems we've faced.

  • Added to My Schedule
    keyboard_arrow_down
    Sean Dunn

    Sean Dunn - Practicing What I Preached: Confessions of a Reformed Enterprise Agile Coach

    schedule  03:45 - 04:30 PM place Mysore Hall 2 people 15 Interested star_halfRate

    Agile coaching is a booming industry -- but what do companies hope to get out of coaching, and what tangible impact does coaching actually have on a team? What happens when you take an agile coach and force them to "eat their own dog food"? This is what happened to me. Join me in my personal journey of transitioning from an enterprise agile coach to a programmer on a team, and what I learned about agile, coaching, and myself in the process. 

  • Added to My Schedule
    keyboard_arrow_down
    Oana Juncu

    Oana Juncu - Blow your self-sealing bubble of Beliefs ... about Agile

    schedule  03:45 - 05:15 PM place Mysore Hall 3 people 13 Interested star_halfRate

    We are drawn to people who share the same beliefs and have had similar relevant experiences. These groups give us strength and a sense of belonging. However, this creates a “self-sealing logic” that can lock out learning, because we state our beliefs as proven evidence. Every missed opportunity of collaboration, may it be at enterprise, organisation, or team level, is a symptom of our inability, as a group, to observe and learn from other group experience and set of values. We are here at the most important Agile Conference, seeking to meet people who have similar experiences, and eventually share same conclusions. What if we were about to create another bubble of "Self-Sealing-Logic" ? 
    The hands-on exercices used in the workshop use "Liminal Thinking", the latest fabulous work of Dave Gray, combined with examples of "Third Culture Kids" profiles. The approach aims to support organisations become continuous learning entities, that reinforce leadership and trigger cultural shift. 
    Session's main goals are :

    • create a space of opportunity to "unlock" our own bubble of beliefs through a set of hands-on exercices, 
    • experience , through the open discussion during the exercices, how learning enhances leadership, 
    • allow the audience to discover Dave Gray's "liminal thinking". We will learn to unveil the impact of our beliefs and start understanding why we have needed them. What were the relevant needs that lead to our assumptions? On the other hand, during the session, we will pick some other "self-sealing logic" group and try to understand without judgement their own process that led them from their own relevant experiences to different beliefs.
16:45
17:20
17:45
  • Added to My Schedule
    keyboard_arrow_down
    Isabel Evans

    Isabel Evans - Leading, Following or Managing? Help your Group Thrive

    schedule  05:45 - 06:30 PM place Mysore Hall people 47 Interested star_halfRate

    We work in teams. Teams that have goals, that work together to solve problems, that sometimes squabble and make up. How people in the group behave depends on the styles of leadership, management and followership adopted in the group, and on each of our individual behaviours.

    Do we have a mentoring, coaching, managing or leadership role towards others? Are we following or learning from others? Do we influence our colleagues and organisations in public or behind the scenes? Are these interactions built into a formal hierarchy in our group? Have we informally adopted an interaction role? Or have we even been forced into a particular interaction role?

    In order that we work together as efficiently and effectively as possible, we need to understand the range of approaches or styles for leadership and management, what styles we feel most comfortable with, and how we react to both being leaders and being led.

    It’s not just humans who work in groups. Other animals can tell us about how we interact with individuals, teams, and groups both as leaders and followers. Isabel discusses animal behaviour, predators, animal groups, parasites and epiphytes, and the richness of symbiotic partnership.

    Regardless of the project model/software life cycle model you use, you’ll need to understand these interactions, and when to adopt a leadership, mentoring, coaching, following or learning attitude in order to help your group thrive.

18:30

    Closing Talk - 15 mins

18:45
20:15

    Dinner and Networking - 45 mins

Agility At Scale

Wed, Mar 8
Timezone: Asia/Kolkata (IST)
08:30

    Registration - 30 mins

09:00
10:00

    Welcome Note - 15 mins

10:15

    Coffee Break - 15 mins

10:30
  • Added to My Schedule
    keyboard_arrow_down
    Jez Humble

    Jez Humble - Why Scaling Agile Doesn't Work

    schedule  10:30 - 11:15 AM place Mysore Hall 1 people 63 Interested star_halfRate

    There are now several frameworks designed to address the demand for “big agile.”

    In this talk Jez will explain the flaws in such frameworks, why they so often fail to produce the desired effects, and what we should do instead. He will also address some common organizational obstacles to moving fast at scale: governance, budgeting, and the project paradigm - and discuss how to address them. Warning: this talk will include liberal use of real, statistically sound data.

  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little - 7 Sins of Scaling and other Agile Antipatterns

    schedule  10:30 - 11:15 AM place Mysore Hall 2 people 18 Interested star_halfRate

     This is about agile “anti-patterns”: “something that looks like a good idea, but which backfires badly when applied” (Coplien). Todd has been around agile development from before it was called agile.  In that time, he’s seen teams fall into the trap of many of these anti-patterns, becoming stuck without ever realizing it. Frequently, this is due to a dogmatic understanding of what is right and wrong about scaling and agile development. The first step to getting unstuck is to be able to detect these “sins.” The presentation aims to expose teams to these common pitfalls and then also provide a vision for a virtuous path to take them to the Promised Land.

  • Added to My Schedule
    keyboard_arrow_down
    Jutta Eckstein

    Jutta Eckstein / John Buck - With Sociocracy, Hierarchy Becomes Agile

    schedule  10:30 AM - 12:00 PM place Mysore Hall 3 people 21 Interested star_halfRate

    Many agile teams suffer from the mismatch of agile and organizational leadership, with the latter being reflected by the organizational hierarchy. Based on self-organization and iterative processes, the agile teams run into trouble with the top-down steering of their environment. Consequently, agile proponents very often believe that a supportive agile organization should be structured without hierarchies, the so called “no managers” approach of “reinvented organizations.” Several companies in the agile field are experimenting with different organizational approaches that don’t use hierarchies. Yet, “no hierarchy” or “no managers” is not an option for many organizations.

    In this session we suggest using sociocracy as a solution that leaves the hierarchies in place in an agile way - an option the organization is free to choose. Sociocracy shows how hierarchies can actually be agile and can strongly support (rather than opposing) agile philosophy. It enables managers to become agile leaders. As a participant you will learn how the principles of shared decision making and double-linking are key to enabling self-organization. These principles convert hierarchies from linear to circular so that they support an agile mindset.

    Sociocracy is a way for groups and organizations to self-organize. Based on four principles (self-organizing teams, shared decision making based on consent, double-linking, and electing people by consent to functions and tasks), sociocracy provides a path for existing organizations to have empowerment and self-responsibility on all levels. Different than comparable methods, sociocracy allows companies to start where they are – with their existing organizational structures and the like. It seems to be a perfect fit for organizations that need to be truly agile (due to market pressure) beyond their IT departments and software teams.

11:30
12:05
12:30
12:50

    Lunch Break - 55 mins

13:45
14:45
15:20
15:30

    Coffee Break - 15 mins

15:45
16:45
17:20
17:45
18:45

    Closing Talk - 15 mins

19:00

    Reception Dinner - 120 mins

Lean Product Discovery

Thu, Mar 9
Timezone: Asia/Kolkata (IST)
08:30

    Registration - 30 mins

09:00
  • schedule  09:00 - 09:45 AM place Mysore Hall people 43 Interested star_halfRate

    Digital proficiency is no longer just "nice to have" for banks; it is a requirement for successful customer engagement and long-term growth. In 2010, the company adopted an agile approach to software development and delivery - launching products in rapid iterations and adjusting them based on customer feedback. The shift to agile helped the bank clarify its development strategy and its customer value proposition. It also prompted ING to redefine its employee value proposition by shining a bright spotlight on the high-quality engineering talent required to lead digital innovation.

    We've digitized our processes to make transactions clear and easy for our customers. We've invested heavily in channels and touchpoints with our customers, introducing mobile and other technologies so that we can offer our services 24/7, anytime, anywhere. We've invested in analytics and in getting a 360-degree view of customers to better empower them to make important decisions about their financial assets. And we've introduced agile ways of working - in particular, a DevOps model.

    If you are interested in learning more about our transformation and vision behind it, this session is for you.

10:00

    Welcome Note - 15 mins

10:15

    Coffee Break - 15 mins

10:30
11:30
12:30
  • schedule  12:30 - 12:50 PM place Mysore Hall 1 people 31 Interested star_halfRate

    At the core of lean product delivery is -of course- the continuous delivery of a product. Yet, how does this impact the architecture, especially when welcoming changing requirements (even late in development)? Basically, the architecture should be enabled to incorporate these changes and therefore to emerge over time. This implies not to finalize the architecture upfront.

    For a small team being jointly responsible for the product delivery AND the architecture this is often already a challenge yet even more so for a large team. But, also for large-scale agile development the requirement for an emergent architecture holds true. However, it is difficult if not unrealistic to expect e.g. 300 team members to decide jointly on the architecture.

    Moreover, the role of and support for the architecture depends not only on the degree of the size of your development effort but as well on the degree of complexity of the system. 

    In this session I report on my experiences using different models for supporting an emergent architecture in different (mainly large-scale) environments that take the degree of complexity into account.

  • schedule  12:30 - 12:50 PM place Mysore Hall 2 people 17 Interested star_halfRate

    In his November 2016 New Yorker article, Om Malik calls out the Silicon Valley juggernauts as a warning to all of us: “The lack of empathy in technology design isn’t because the people who write algorithms are heartless but perhaps because they lack the texture of reality outside the technology bubble."[1] 

    But the onus isn't just on the juggernauts of this era but on every one of us to understand and put into practice what empathy is - without it, we will fail to impact our products, our consumers and ultimately a world full of human lives with the potential we could. 

    Because every product, platform, service or offering will end with the consumer, empathy is the first crucial step in the development lifeline to delivering impact.

    Failing to recognize actual humanity as central to what we do is an easy (and hidden) trap.  We are surrounded by data and by technology and the temptation to forego the non-personable aspects that define people, the beings for which the ‘thing’­ is being created, in favor of relying on our data and technology, is veiled as logical. 

    In this session, we will explore empathy as a concept, talk about why and where it belongs in the technology and product design space and how to help your teams develop and keep this skill central.

    [1] http://www.newyorker.com/business/currency/silicon-valley-has-an-empathy-vacuum

  • Added to My Schedule
    keyboard_arrow_down
    Manish Chiniwalar

    Manish Chiniwalar - Lean Startup from the Trenches

    schedule  12:30 - 12:50 PM place Mysore Hall 3 people 21 Interested star_halfRate

    Lean Startup is a great process to build new businesses. But when it comes to going from theory to practice, our faith in the process is tested and most often, teams give up to a "seemingly" simple and faster approach of building produces - based on gut feel and seeing what sticks.


    It’s a Friday evening. There are two people in the conference room and they have been talking to their laptops for about 15 minutes. Vaidy is the founder and Arun is a Product Manager. At the other end of the Skype call, is an owner of a well-known yoga studio in Bangalore.

    Another 15 minutes go by and Vaidy mentions “We’ll charge 5% of all the transactions that go through GoodKarma.”

    GoodKarma is an application with a mission to help yoga practitioners grow through deliberate and consistent practice. One of the shorter-term goals of GoodKarma is to help yoga studio owners run their studios better.

    The person on the other side gets worked-up “5% is just too high!” Vaidy calmly justifies why 5% is, in fact, a small number for the benefit he is getting.

    Another 10 minutes go by. Arun and Vaidy are high-fiving!
    They’ve just signed up the 5th customer this month, who’s agreed to start a trial on GoodKarma and be a paying customer.

    Vaidy: “We better start building the product, fast!”


    In this talk, I'll present our story of building a product using Lean Startup methods. How we went from an Idea to the story above and then shipping the product out. The challenges we faced and how we overcame them.

12:50

    Lunch Break - 55 mins

13:45
  • schedule  01:45 - 02:30 PM place Mysore Hall 1 people 24 Interested star_halfRate

    As the co-founders of Intentwise we strongly believe in few things;

    1. Customer discovery and product discovery cannot be done in isolation.

    2. Search and Discovery at every step

    3. Technology enables business and in itself is not a business

    To build a strong product you need to listen and hear to the customers who live and breathe the problems day in and day out. We would like to share our story on how we abide by some of the above principles and guidelines in building some amazing products to help our clients to derive their customer intents.

  • schedule  01:45 - 03:30 PM place Mysore Hall 2 people 45 Interested star_halfRate

    You have a great idea and you want to build the product and launch it in market as soon as possible. Before anyone else can launch it. Great! But building the product takes time, money and opportunity cost. While building and launching a successful product, several things can go wrong:

    • Have you really understood the core problem from the user's point of view?
    • Will your users like the user experience?
    • Have you validated your core-loop which makes your product very engaging?
    • Is your business model flushed out and validated?
    • And so on...

    So how do you minimise these risks? 

    In this 90 mins workshop, you will run some real tests with real users to de-risk yourself and gain validated learning.

  • Added to My Schedule
    keyboard_arrow_down
    Jeremy Kriegel

    Jeremy Kriegel - Sketch You Can! Demystifying a Powerful Collaboration Technique

    schedule  01:45 - 03:15 PM place Mysore Hall 3 people 30 Interested star_halfRate

    "This meeting is a waste of my time."

    When was the last time you had that thought? Was it because the conversation wasn't focused, or people couldn't agree, or maybe they were in violent agreement, but couldn't see it? How easily do you think you can get this meeting back on track? In this session, you will learn a skill that you can apply on the spot that will help you focus the conversation and drive to consensus. Everything you need is probably already in the room.

    This technique is specifically for conversations around the features, functions, and behaviors of your product. Most people are visual thinkers, so give them something visual to focus on. You can do that by walking up to the whiteboard and drawing out what people are talking about. By visually capturing the conversation in a public way, you will help all participants understand each other and come to consensus faster. But I can't draw, you say. Neither can I, and I’ve been successfully using this technique for over 15 years. If you can draw a straight-ish line and a box, you have all the drawing skills necessary.

    In this engaging workshop, you will learn how to create a basic sketch of an interface using some simple sketching techniques and UX principles as well as practice thinking-on-your-feet that will help you comfortably do this with a group.

    I have used this technique to help teams focus the conversation, visualize the requirements they were requesting, quickly experiment with new ideas, and provide detailed input that I can use to design the outcome. Often, the sketch (or a photo of it) acts as the deliverable for simple problems, eliminating the need for more formal wireframes. This technique is accessible to everyone. You don’t need any special software and anyone on the team can use it. Pick up the pen and get on track again.

14:45
15:20
15:30

    Coffee Break - 15 mins

15:45
16:45
17:45
18:45

    Closing Talk - 15 mins

19:00

    Social Event with Reception Dinner - 120 mins

Continuous Delivery & DevOps

Fri, Mar 10
Timezone: Asia/Kolkata (IST)
08:30

    Registration - 30 mins

09:00
10:00

    Welcome Note - 15 mins

10:15

    Coffee Break - 15 mins

10:30
11:30
  • schedule  11:30 AM - 12:15 PM place Mysore Hall 1 people 35 Interested star_halfRate

    Pyramids? Quadrants? Cupcakes?! There are a wide array of models that describe approaches to test automation strategy and their possible positive (or negative) outcomes.

    In this talk, we’ll survey the landscape of testing models: models that range from technical to product to cultural mindsets, including best practices and anti-patterns. I’ll add detail and nuance to each of these models in the form of professional experience, real world example, and case study. 

    With a new lens, focusing on testing strategy as an act of curation, I'll share a new approach to evolving a testing strategy appropriate for your product development team's specific context.

  • schedule  11:30 AM - 12:15 PM place Mysore Hall 2 people 18 Interested star_halfRate

    By working with some of the most successful tech-product companies, I realised that code is NOT an asset, it's a liability. We should strive hard to minimise code. In 2011, when I started to hack on ConfEngine, I questioned my belief in TDD. I had also started playing around with APL style Array-Programming and Functional Programming. I felt, may be, I was getting a bit too dogmatic about TDD and automated tests in-general. As a thought experiment, I decided to build ConfEngine without ANY automated test. At first, it was really scary not to have the safety-net of automated test (something I took for granted for almost a decade.)

    As I scaled ConfEngine without any automated tests, I had certain interesting realisations:

    • How to embrace Simplicity and Minimalism WITHOUT automated tests
    • Why Throwing Away Code frequently helps you achieve a better decoupled-design and how this helps in better experimentation
    • Fear of Refactoring WITHOUT Tests is over-rated (Good IDE and safe-refactoring techniques can take you a long way)

    ConfEngine grew from a pet-project to a 8 member product team. It has over 60K users and has done financial transactions worth over half-million USD. And we continue to push forward without ANY automated tests. Its not perfect, but it has certainly helped me challenge my dogma around TDD.

    Background: In 2001, I stumbled upon the Test Infected paper. For the next 2 years, I struggled to really apply the test-first concept on real projects. Finally in 2003, I felt that I had fully internalised TDD and was able to apply on almost all projects. Then I started playing around with FIT and FitNesse, using ATDD on some of the projects. In 2006 I published "Avatars of TDD" paper in which I explained various styles of TDD and its design implications. Until 2011, I was a very big advocate of TDD, ATDD and BDD. I still like those practices, however I would not recommend it in all projects.

12:30
  • Added to My Schedule
    keyboard_arrow_down
    Prasad

    Prasad - DevOps lead IT Transformation story of an Investment Bank

    schedule  12:30 - 12:50 PM place Mysore Hall 1 people 39 Interested star_halfRate

    Total cost of ownership of the Investment Bank IT portfolio is way too high. Business is also keen in getting high responsiveness from IT. There is high desirability from all stakeholders in changing the way IT work. Based on a value stream analysis, key  aspects that impede speed and value are identified. Common and prominent impediments identified are silo, handovers, local optimization, manual and inefficient software engineering.  Principles and practices of DevOps seems to be an excellent fit for this change. This means new capabilities for IT workforce, new operating model, new way of measuring, new way of aligning with other corporate groups like security etc.  This session is a journey in progress of IT transformation using DevOps as core theme.  Where to begin? What to change? How to create capabilities? How to onboard teams into this wave? How to sustain? Where are we now? Where we want to reach? Lessons learnt?

  • Added to My Schedule
    keyboard_arrow_down
    Pooja Shah

    Pooja Shah - Release Status Analyser to bring more agility @ work

    schedule  12:30 - 12:50 PM place Mysore Hall 2 people 18 Interested star_halfRate

    Problem Statement

    Do you have a lot of automated Tests and so the lot many tests reports to analyse before taking call for release?

    Plot: Any huge impacting micro-service based product/project for which enormous tests have been already automated and your continuous deployment process requires all of those tests in "PASSED" state. Due to high traffic most of the day, releases are deployed at non peak hours. Imagine decided deployment time in production is 5 AM. (The feature and regression testing is done already but there are always some small last minute changes, so it’s better to have a double check on the frozen code to release)

    At 1 am: Final automated sanity checks start executing  

    At 3 am: Get the results, release engineer/ devOps gets notified of the state of the release, she/he looks at CI board and see several green and red builds. He/She now 1 by 1 opens all red builds, clicks on individual reports, console, screenshots....  more red builds- more time to analyse it...

    At 4.30 am: After gathering report on which test failed for what reason & who should be looking at them, she/he calls up respective owners to look out and state the reasons & take a call on the release

    At 5 am: The service owner says "let’s revert my feature to previous version and take the release live"

    Release Engineer again starts searching for files/mails where the last stable version is stored, spending more time again. It’s 6 AM now, she/ he deploys last stable service versions, runs the failed tests -> integration tests ...

    it already 9 AM, wooosh!, time runs really fast. Can't release now, peak traffic time.............

    Do you share the same pain?

    Before giving a +1 for the release, it becomes essential for the QA folks to provide proper feedback as quickly as possible. At the same time assessing n number of reports becomes an additional tedious task. So definitely there should be 1 dashboard which nicely displays the status with transparency and anyone should be able to tell whether release is good to go and if not, then why not. RSA which I have created on top of open-sourced technologies is a small effort towards achieving the same. Will take you through a live demo and discuss on how you can use it to meet your needs.

  • Added to My Schedule
    keyboard_arrow_down
    Mikhail Advani

    Mikhail Advani / Rajesh Tamhane - DevOpSec: Rapid Security in the Cloud with AWS and CIS

    schedule  12:30 - 12:50 PM place Mysore Hall 3 people 23 Interested star_halfRate

    High performance teams are releasing software to production several times a day. This poses a challenge to Ops and infosec who need to have the confidence that  these releases will not lead to a security breach in the infrastructure. DevOpSec or DevSecOps is a discipline where development, operations and  security work collaboratively to achieve security  compliance in agile teams. In this demonstration of our open source project, we show how we used DevOps and security best practices to achieve and test AWS infrastructure.

12:50

    Lunch Break - 45 mins

13:35
14:30
15:05
15:15

    Coffee Break - 15 mins

15:30
16:30
17:00
17:45

    Closing Talk - 15 mins

Post-Conference Workshop Day 1

Sat, Mar 11
Timezone: Asia/Kolkata (IST)
09:30

    Registration - 30 mins

10:00