Agile India 2017 is Asia’s Largest and Premier Conference on Agile, Lean, Scrum, eXtreme Programming, Lean-Startup, Kanban, Continuous Delivery, Lean UX, Product Discovery, DevOps, Enterprise Agile, Patterns and more…
Smart Pricing is still available as of 11 January. REGISTER TODAY before prices increase!
Isabel has more than thirty years of IT experience in the financial, communications, and software sectors. Her work focuses on quality management, software testing and user experience (UX), She encourages IT teams and customers to work together, via flexible processes designed and tailored by the teams that use them. Isabel authored Achieving Software Quality Through Teamwork and chapters in Agile Testing: How to Succeed in an eXtreme Testing Environment; The Testing Practitioner; and Foundations of Software Testing. A popular speaker and story-teller at software conferences worldwide, Isabel is a Chartered IT Professional and Fellow of the British Computer Society, Programme Secretary of the BCS SIGiST, and has been a member of software industry improvement working groups for over 20 years.
Joshua is a globally recognized thought leader in Agile and Lean software development. He is an entrepreneur, author and programmer passionate about excellent software and discovering better, faster and safer ways to produce it. As the founder and visionary leader of Industrial Logic, Joshua is currently defining what it means to practice modern agility. Modern agile practitioners work to Make People Awesome, Make Safety A Prerequisite, Experiment & Learn Rapidly and Deliver Value Continuously. Joshua is a sought-after international speaker, author of the best-selling, Jolt Cola-award winning book, Refactoring to Patterns, and a guru-level practitioner of Lean/Agile methods. His pioneering work in Agile processes has helped popularize Agile Readiness Assessments, Chartering, Storytest-Driven Development and Iterative Usability, many of which are now standard in Agile/Lean processes. He is an active blogger on forward-thinking, modern software topics with an edge.
Dave Thomas, Chief Scientist/CSO, Kx Systems, Co-Founder and past Chairman of Bedarra Research Labs (BRL), creators of the Ivy visual analytics workbench and ACM Distinguished Engineer. Founder and past CEO of Object Technology International (OTI), becoming CEO of IBM OTI Labs after its sale to IBM. With a unique ability to see the future and translate research into competitive products, he is known for his contributions to Object Technology including IBM VisualAge and Eclipse IDEs, Smalltalk and Java virtual machines. Dave is a popular, humorous, albeit opinionated keynote speaker with an impressive breadth of business experience and technical depth. He is a thought leader in large-scale software engineering and a founding director of the Agile Alliance. With close links the R&D community Dave is an adjunct research professor at Carleton University in Canada and held past positions at UQ and QUT in Australia. He has been a business and technical advisor to many technology
companies including Kx Systems. Dave is founder and chairman of the YOW! Australia and Lambda Jam conferences, and is a GOTO Conference Fellow.
Rajesh spent more than 15 years in the Silicon Valley, working for companies like Digital Equipment Corporation, HP, Google and Motorola. He joins Hike from Motorola where he was most recently the Director and Head of Wearables and Internet-of-Things software. Rajesh’s expertise lies in creating scalable, consumer-facing software products in the mobile space, overseeing end-to-end engineering & product development life cycle, and building cross-functional teams. Offering in-depth business and technical acumen, complemented by strong expertise in shaping product strategies into tangible products, strengthening stakeholder alliances, integrating Agile best practices, and streamlining processes that increase revenue, lower costs, and create business value.
Nate is the Managing Director at the San Francisco office. In his role, he blends the decisiveness and collaborative skills of a product manager with the acumen of an economist to build bridges with people and organizations. Equal parts teacher and student, Nate leads initiatives in content creation, business development, and creative leadership.
At Cooper, he helped United Airlines find new ways to reward loyal customers, led an effort at GE Healthcare to create a strategy for the international expansion of a key product line, and designed solutions for workplace collaboration, delivering technology to schools, and the future of the connected kitchen. Before Cooper, Nate led design and product management at BuildZoom, and was a Director of Product Management at Thomson Reuters.
Mitchell Hashimoto is best known as the creator of Vagrant, Packer, Terraform and Consul. Mitchell is the founder of HashiCorp, a company that builds powerful and elegant DevOps tools. He is also an O’Reilly author. He is one of the top GitHub users by followers, activity, and contributions. “Automation obsessed,” Mitchell solves problems with as much computer automation as possible.
Jez Humble is co-author of the Jolt Award winning Continuous Delivery, published in Martin Fowler’s Signature Series (Addison Wesley, 2010), and Lean Enterprise, in Eric Ries’ Lean series (O’Reilly, 2015). He has consulted for many Global 500 companies to help them achieve technical excellence and deploy a culture of experimentation and learning. His focus is on helping organizations discover and deliver valuable, high-quality products. He is co-founder of consulting company Humble, O’Reilly & Associates, and teaches at UC Berkeley.
PRE/POST CONFERENCE WORKSHOPS
Workshops have very limited seats. BOOK EARLY to ensure you don’t miss these great opportunities!
Much has changed since the publishing of the Agile Manifesto in 2001. Pioneers and practitioners of lean and agile methods have examined weaknesses and friction points, experimented with simpler approaches, and produced agile processes that are safer, simpler and far more capital efficient. The result is modern agile. It’s values-driven, non-prescriptive and an easier starting point than antiquated agile processes. Modern agile amplifies the values and practices of organizations that have discovered better ways to get awesome results. Are you still cramming low-quality work in the end of each sprint, struggling with growing technical debt, arguing about “definition of done” or frustrated that “management/product never gives us time to do it right?”
In today’s business environment, the user experience and the commercial imperatives have become overwhelmingly important. As testers, it is vital that we understand quality in use and the user experience, in order that we focus our tests correctly.
“Quality in Use” measures human, business, and societal impacts of products (usability, accessibility, flexibility, commercial, safety). This builds to a User Experience (UX) and are underpinned by technical and engineering qualities. For the people selling, supporting, or using the products, this is the beating heart of the customer experience. Without these “big picture” attributes, delivered software will not be acceptable, may result in reduced profits, and may not be legal. In the tutorial, Isabel will use examples from real projects to discuss how to design tests derived from the user personas, contexts of use, and acceptance criteria.
Leaders today face constant, accelerating change driven by technology and incredibly high expectations from both internal and external. As IT leaders, we need to transform our roles and our departments. In this workshop, we focus on, teach and practice the tools of transformational leadership. 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.
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. The one-day workshop is not technical and is suitable for all team members. The workshop is also valuable for management tasked with moving from traditional approaches to agile.
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.
Testing of mobile apps is easy to do poorly, however, we don’t need to be constrained by mediocrity. Instead let’s learn about the foundations of how mobile platforms and development technologies are used to create apps and how these are then interpreted by the devices the apps are installed on so that we know the sorts of bugs and problems that affect many mobile apps i.e. testing techniques that may be generally applicable to most apps.
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.
Let’s explore the purpose and use of estimates in the management of software development efforts, and consider possible alternatives. Why do we estimate and are we making estimates that are actually useful? In this session we’ll participate in some interactive information gathering exercises to see if we can gain a shared idea of our current understanding of the purpose and use of estimates. We will examine the nature of software development projects and explore some real data to shed light on the art and science of software estimation. Our exploration goal is to see if we can work together to come up with some ideas about improving on the traditional approaches to using estimates.
Getting software released to users is often a painful, risky, and time-consuming process. The practice of continuous delivery sets out the principles and technical practices that enable rapid, low-risk delivery of high quality, valuable new functionality to users. In this workshop, Jez Humble presents an in-depth guide to the principles and practices behind continuous delivery and the DevOps movement, along with case studies from real companies and ideas to help you adopt continuous delivery and DevOps within your organization.
Once upon a time, we had ‘Discovery’, ‘Define’, and ‘Design’. These phases let us explore the problem and the audience, while conceiving a holistic solution. Now we have sprints, complete with a backlog that seems like it appears overnight and a development team that is going to build with or without design to guide it. How do we continue to create great products? This 1-day workshop enables you to engage your clients and stakeholders to quickly define the key elements of your product or project, aligns the team, and identifies critical risks. When it is complete, everyone has a good idea of what is going to be built as well as what it will take to get there.
Today companies are expected to be flexible and both rapidly responsive and resilient to change, which basically asks them to be Agile. Yet, doing Agile (the mechanics) is different from being Agile (the mindset). The mindset lets you apply flexible Agile patterns not only for software development teams but for whole company. In this workshop, we will examine what being Agile really means and how it can be implemented by combining principles from the Agile Manifesto, Sociocracy, Beyond Budgeting, and Open Space. We’ll draw on everyone’s experiences to show the path to transforming our companies into agile enterprises – from Board to janitor, offering concrete tools and methods that participants can apply right away.
In the early 2000s, eXtreme Programming (XP) introduced agility to software engineers. Contemporary cultural and technical innovations – container technology, distributed version control systems, the proliferation of free and open source software, and the DevOps movement – have significantly expanded our possibilities.
In this one day, hands-on workshop, we’ll build a modern continuous deployment pipeline based on Git, Jenkins, and Docker.
Also there was a proportionate drop in the number of sponsors. 14 sponsors in 2014 as opposed to 11 in 2015. So many people ask us why the numbers dipped? That’s a fair question. Following are the reasons why we think the numbers dipped:
We moved from Four 1-day mini-conferences to Two 2-day mini-conferences. (So naturally the count will dip. In 2016, we are back to Five 1-day mini-conferences.)
In 2015, we shrunk the program team size to 9 members from 29 members in 2014. Reason: we wanted to experiment and see what happens if we don’t decide the team upfront, but add members to the team only based on their contributions (esp. via the Submission System.) I guess that did not work out all that well. In 2016, we are back to a 26 member team that is decided upfront.
Overall the planning for the 2015 conference was delayed. Only in Sep 2014 we started actively working on the conference. As opposed to starting in July 2013 for the 2014 conference. (For 2016, we started work in June 2015 itself.)
Part of the reason for the delay was because, we were busy planning the Agile Pune 2014 Conference. Now planning 2 fairly large, international conferences on the same topic, 4 months apart, can lead to them competing with each other. Each year we do organise a bunch of smaller, regional conferences. However with the Pune conference we got bit ambitious. A good lesson learned.
This does not mean we will stop experimenting. We’ve been successfully running this conference for 11 years and every year we try something new, something different. That’s what keeps the excitement & enthusiasm for us (a group of volunteers, with regular day-time jobs.)
With the increase in the consumer demand and change in the market dynamics, the number of new products that are launched in our market have increased tremendously. The passion of these young entrepreneurs have inspired thousands of young minds to develop new solutions to new/existing problems. However the success of these products are largely driven by the consumer expectation and passion is only a driving force.
Ash Maurya, a serial entrepreneur is running a 2-day workshop about building successful products at Agile India 2014. In this 2-day hands-on workshop, you’ll learn a systematic methodology, developed through rigorous testing of Lean Startup, Customer Development, and Bootstrapping techniques on hundreds of products, that will show you exactly how to build what people want.
He is the founder of Spark59 and also the author of ‘Running Lean’. Currently he is working on his new book ‘The Customer Factory’.
We had a short chat with him to understand his views about building successful products.
1. What is one important lesson that the large enterprises should learn from startups and vice versa?
Bringing a new product to market, whether at a large enterprise or startup, is riddled with extreme uncertainty. Most products fail.
The key to raising these odds is prioritizing learning around what’s riskiest (not easiest) in the business model.
The first phase of the journey is getting to a business model that works. This can be characterized as a “search” problem where speed is key. The best mode of operation here is the startup. Enterprises that want to explore new or disruptive innovation should model themselves after startups.
The second phase of the journey is scaling that business model. This can be characterized as an “execution” problem where systems and processes become increasingly important. Here the startup needs to mature it’s practices and can learn a lot from existing enterprises.
2. How does Lean Startup help companies to deliver a customer centric product?
The job of a business model is to create, deliver, and capture customer value.
The Lean Startup embodies the customer in every part of the process. All experiments have to end in customer learning and you aren’t making progress until you can demonstrate customer value.
It is through this continuous feedback loop with customers that we break the product development silo and build more products that people want.
3. Your Lean Canvas is an excellent tool to help companies articulate their business model in a simple format. Are there any gotchas that companies should be aware when using the Lean Canvas?
The biggest pitfall with any kind of modelling is falling into the analysis/paralysis trap. I recommend time-boxing business model creation to no more than a day and then shifting all the effort to business model validation using the other tools in the Lean Stack suite.
4. India has a budding Startup culture. What would be your advice to startups?
I truly believe we are going through a global entrepreneurial renaissance which represents an incredible opportunity for all of us.
But while we are building more products than ever before, the sad reality is that the success rate of these products hasn’t changed much.
The odds are still heavily stacked against starting a new business and most of these products will unfortunately fail.
The good news is that a lot of these big bang failures can be outright avoided and instead replaced with a more systematic approach to building successful products.
The number one reason why products fail is not because we fail to build what we set out to build but because we waste needless time, money, and effort building the wrong product.
I attribute the entrepreneurs unbridled passion for their solution to be the top contributor to this failure.
The key is shifting your perspective from having more passion about just your solution to having as much (if not more passion) for your customers and their problems.
5. What is the take away from your Running Lean workshop ?
This will be hands on workshop with part lecture and part hands-on exercises where you will work on moving your business forward using lean techniques.
The first day will be all about modelling your business into a more more manageable and testable framework. While the second day will be all about stress testing this business model through carefully designed experiments.
By the end of this 2-day workshop, you will have an actionable plan for what to do next to move your business or product idea forward.
Goals: Learn and practice Agile by doing Agile. Build community. Make art!
The concept: During three evenings, we’ll create a visual art piece together. We’ll create new connections among attendees and build and reinforce the community of Agilists in India and around the world. On the fourth day, we’ll display our art. Finally, we’ll give pieces of our art as gifts to each other to take home with us as reminders of our potential to create greatness together.
The art piece will be a large two-dimensional wall hanging. The center of the piece will be the Agile India logo. We’ll create both the central theme and smaller scale contributions that represent each of us as individual people. We’ll get help from a small team of artists and designers from McAfee in Bangalore.
We’ll use Scrum to execute the piece during the first 3 evenings of the conference. We’ll work in 1-hour sprints to create the piece in three-hour-long sessions. Richard Kasperowski will play Product Owner, Nagendra Kumar will play Scrum Master, and the attendees will be the Development Team. Every hour, we’ll plan our sprint, do the work, hold a review, and retrospect to improve our creativity and velocity toward our goal-to complete the piece and hang it on the wall by the end of the third day.
Here is a small video, which demonstrates a similar art event:
On the morning of the fourth day, we’ll unveil the piece, and it will be available for attendees to enjoy. During the afternoon of the fourth day, we’ll dismantle the project by offering pieces of it as gifts to each other to take home. Thus the piece will be both ephemeral and permanent. The unified piece will exist for only a short time, the fourth day of the conference, before we dismantle it. Small individual pieces of art will live on permanently in the homes and offices of the people who take them home with them, as reminders of the community, and as symbols of the power of art and Agile to create greatness together.