Registration and Vendor availability
by Jagdish Karira
Perhaps the most dreaded question asked any of Information Technology (IT) Professional is "How fast can you deliver?" This session will provide the audience with insight into planning and estimating techniques, and proven Agile practices; so that they can answer the most dreaded questions effectively. By developing more reliable plans, IT professionals will learn how to deliver predictably, report green dashboard status consistently and minimize Go-To-Green escalations. The session will focus on advanced concepts of Agile estimating such as Multi-level Planning, Product and Release Planning and Relative Sizing. Participants will learn how effort, complexity and uncertainty impact estimates. Agile fundamentals will also be covered for IT professionals who are new to Agile.
Participants will learn about story points, ideal days, and how to estimate with "Planning Poker" Learning Objectives Participants will learn:
1. Agile Delivery Model
2. Product and Release Roadmap
3. Impact of Agile on PMBoK Knowledge Areas
4. Proven Planning and Estimating Techniques
5. How to estimate in Distributed Agile Delivery Model with Virtual Teams?
git gone wild: how to recover from common git mistakes. "Oh no! I just typed something into git and now my work is gone! Ahh!" Don't panic.
Contrary to popular belief, git is one of the most non-destructive version control systems available. When used right, git never loses any data, and even when misused, chances are very high you can still recover. This talk will present turn-by-turn directions on how to recover from a wide array of common git mistakes, and also provide some workflows to minimize them.
Examples include, but are not limited to:
* Changing spelling errors in commit messages.
* Split commits into multiple commits with logical separation.
* Combining multiple commits into one.
* Resetting the base commit when you accidentally branch off of the wrong branch.
* Recovering from merge conflicts. As well as more advanced topics, such as:
* Extracting parts (e.g. sub-directory) of a repository as a new repository.
* Merging multiple repositories into one while retaining version history.
* Removing confidential data accidentally committed.
by Daniel Davis
In this session we'll discuss the basis for a few popular phrases that get tossed about these days. "Stop Thinking & Start Doing", "Execution is Everything", "It's 1% Idea, 99% Execution", etc... We probably don't have a problem agreeing that they are worthy goals, but why then are they so hard to achieve? This question is the focus of the session, as we'll attempt to understand the reasoning behind it and explore the Agile Methods/Practices that help in this regard.
by DJ Daugherty
The session will take a deeper look into the ideas around testing beyond the normal TDD thoughts on tests. We will dig into the business value behind the documentation created by tests, the ability to better engage developers into the business process, the ability to compare requirements over time, and the removal of fear around the practice of refactoring... plus many more. It will be a fun journey allowing developer-types and business-types alike come to a common understanding of why tests are important.
This fast paced session is like 'speed dating' for Agile tools. What is in your toolbox? Are there tools that could help you be more effective or improve? This presentation has a unique format with no bullets. Also, I will be using a complete basketball scoreboard with shot clock to keep me on schedule! Everyone should come away from this session with a few new ideas to try. It is a great cross pollination event as well, as input from the audience will be solicited and shared. (Also, I am not endorsing or 'selling' any tools)
by Steve Boone
As companies continue to grow into their agile capabilities, the speed of development continues to grow. Development teams have mastered the art of Continuous Integration and are trying to break down the doors to Continuous Deliveryâ€¦ but Operations teams hold the keys! Today, when a deployment fails it usually results in several emails and phone calls between development and operations. What failed? Where are the logs? On what machine(s)? Who approved this deployment? Why didn't we catch this problem earlier? These are the typical questions that get asked and lets face it, rarely does anyone have the answers. Time is wasted, systems are down, and fingers are being pointed. These headaches are easy to avoid. DevOps is an approach at bridging the gap between development and operations. For continuous delivery to be successful into secure production environments many aspects need to be accounted for besides simply deploying builds. Application configuration, environment configuration, topology differences among environments all present challenges in releasing quality software on time.
In this talk we will cover:
- What is DevOps, and how did we get here?
- Pushing the quality metric.
- Common enterprise patterns that DevOps can solve
- PaaS: Scaling for the future
by Dan Neumann
Let's go beyond the rules of agile frameworks. Come to the "principles" office, and explore the foundation of agile methods.The principles shed light on the reasons for some of the rules behind Scrum and Kanban. The principles also guide you as you explore scaling beyond the team level, or when you encounter novel situations. When you leave this session, you will have done three things. First, you will explore the principles and their presence or absence in your team or company. Second, you will have identified activities or beliefs in the organization that either promote or inhibit agility of the principle. Third, you will have learned about some strategies for starting and sustaining change. Having done these three things in the workshop, you will leave with a framework to apply when you return to work and continue on your agile journey.
Demystify challenges in continuous software development by learning the importance of addressing Technical Debt. Leave with a new perspective and fresh ideas on how to explain it to others, even the non-technical. Hear real world examples and situations to relate the jargon filled technical world of software development to everyday life using Technical Debt as a metaphor referring to the eventual consequences of poor or evolving software architecture and software development. Understand short term and long term impacts of uncompleted changes within a codebase, and most importantly, learn techniques on how to address it.
by JD Sallee and Edgardo Engalan
Agile software development has reached mainstream adoption, yet many practitioners are still struggling to realize any of its benefits. Too often, teams focus on the mechanics of agile practices as opposed to the principles that define agile's true value. In his talk, JD Sallee will focus on several of Agile's guiding principles and describe how they are key enablers to developing high performing agile teams. He will use two specific simulations (The Marshmallow Challenge, and The Modified Penny Game) to highlight principles like using working software as a measure of progress, value based prioritization, one piece flow, optimize the whole, and continuous improvement.
Whether you are a new to leading teams or an experienced lead, this session will help you to gain hands-on tools and techniques for facilitating high performing teams that you can put into practice right away. We will introduce some agile process improvement techniques such as using our agile cards/sticky notes to improve brainstorming exercises and resolve complex process issues. We will discuss the importance of being a neutral facilitator, key ground rules for creating an environment that encourages open communication, tips and techniques for handling "difficult" team members, "war stories" that derail team momentum, and how to create a "level playing field" so all team members participate in the discussion. This is intended to be an interactive session and participants are encouraged to share their best practices as well so we can all learn and grow!
The basics of Test Driven Development (TDD). This session will cover the reasons why we TDD, the principles behind it, and hands-on exercises to cement the lessons. Participants will need to bring a charged laptop (or pair up with someone who has one), but we'll keep the rest of the requirements as minimal as possible.
Transforming to Agile practices is difficult, perhaps even more so for public sector government organizations. In this session we'll give an experience report for how we brought these practices into a public sector organization with a 280 person IT department (4300 organization wide) and how we're branching out into other public sector organizations as a result. While the initial scope of the internal coaching team was the IT group, we'll show you how we were able to spread influence to other areas of the organization including the PMO, HR, Learning and Performance (L&P) and Change Management departments despite the additional constraints that come along with working in a government organization.
In a year we've been able to migrate the entire 280 person IT group to Agile, added Agile training curriculum to the official leadership program through HR, helped transform the PMO, and develop technical capability to better support delivery of software. We'll show you the progress we've made and the process we used to get there.
Some of the topics we will touch:
Anzen. It's a foundation of Maslow's Hierarchy of Needs and a pillar of the Toyota Way. It helped a 100-year-old, 60,000-person aluminum manufacturer regain its greatness, and it powers the software products that millions of people love. If you study every Lean or Agile principle and practice, you will find it's a common denominator. Anzen is the Japanese word for safety.
When Anzen lives within a software product, it just works; people regularly use and recommend it; engineers modify it without fear; it contains few defects; it can be deployed with ease; it is immune from threats; and it helps protect the organization's finances, reputation and investors. Anzen lies at the heart of excellence.
Anzeneers are empowered to engineer anzen into everything, from their culture to their workspaces, from code bases to processes, from products to services. They use short feedback loops to protect time, energy and money. They use automated testing, continuous builds, refactoring and collective ownership to protect development. They use minimum viable product, validated learning and innovation accounting to protect resources and stakeholders. They use visualized work and limited work-in-process to protect teams from bottlenecks and decreased flow. And they use Lean interaction design and usability evaluation to protect people from poor user experiences.
In this talk I will share what I have discovered about anzen, including why it promotes safe risk taking, how to identify faux safety, when it can be taken too far, challenges of growing an anzen culture and what it means to be an Anzeneer.
by Mark Hammer
In most organizations, developers may review each other's code, product managers may review each other's stories and quality teams may review each other's test plans. But what if the extended team reviewed these materials cross-functionally so that quality teams reviewed (or at least had visibility into) user stories â€“ and testers saw user stories? In today's fast-paced Agile world, teams have to collaborate in order to be successful. Mark Hammer describes how peer review practices can succeed where more cumbersome methods fail. He uses concrete examples of teams that have embraced cross-functional peer review of user stories, code and test plans in an Agile environment, and how this has resulted in higher quality products developed faster. Mark offers tips on the mechanics of tool-based code reviews and compares five common styles of review, presenting research from Karl Wiegers, Frank W. Blakely, Mark E. Boles and others. He also looks at real-world examples including that of a customer who made the changes the research suggests, and reveals results, which are impressive. Attendees leave with an understanding of how cross-functional peer review can improve the performance of individual members of the extended product development team, including product management and testing team as well as their teams.
by Gerry Kirk
Need buy in from a key manager or executive to adopt Agile? Desiring better team collaboration? Hungry for a saner life at home?
Try Personal Kanban, winner of the Shingo prize for Operational Excellence. It's the fastest, simplest way to taste test the goodness of the Lean Agile approach to managing knowledge work. Personal Kanban empowers small teams and individuals, at work and at home.
Give that overwhelmed executive instant relief. Build your own system, and soon curious onlookers ask and then create their own. Look out, you've just released an Agile virus in your organization!
You've also discovered a way for you and your team to get more out of your efforts, to improve communication, and find time for the things that matter most.
In this session you'll learn how to create a Personal Kanban system through stories, examples and interactive exercises. Walk away understanding the psychology behind visualizing work and limiting work in progress, inspired and motivated to make a difference at work and home.
by Rob Keefer
Innovation and lean strategies are getting a lot of attention. And for good reason. They really work. Numerous small players are leap-frogging large players with lean tactics, such as minimal requirements, small cross-functional teams, iterative development, learn-as-you-go thinking, and more. "The Lean Start-up" is a proven phenomenon.
But what if you are NOT a start-up? What if you are a large operation facing obstacles of complexity, compliance, current culture, and more? Using these strategies in the wrong context will make it seem like you're moving backwards--even leaving you longing for the way you were. The reality is: you need to navigate differently.
But how? This session will focus on how you can incorporate best practices from the Lean Start-up world, and tailor them to fit your reality. We'll cover proven lean principles learned over years of complex business application development that you can apply to your next initiative. Weâ€™ll address critical adaptations to the Lean Start-up model to allow for complexity and other common obstacles. You will learn actionable steps you can take on your initiatives--software related or not. If you follow our guide, you will be acting more like a Start-up in no time.
Participants will be able to:
Identify what an effective Minimum Viable Product (MVP) is for a complex effort and how it differs from the more typical Start-up effort.
Learn to plan initiatives differently, focusing on priorities that maximize learning and business value.
Apply methods to make quick improvements and optimize efforts--while still operating within the realities of complexity, compliance, and current culture.
Identify areas today where they can start to act more like a Start-up.
by Jeff Morgan
Many organizations are introducing test automation only to find out it is more difficult than they thought it would be. Good test automation requires good coding practices. Good test automation requires good design. To do anything else will lead to spaghetti code that is hard to maintain or update. If you're new to coding or new to automation it is difficult to know where to start. Join Cheezy as he talks about and demonstrates lessons he has learned while helping numerous organization adopt test automation. He will show you the patterns he uses to keep automation code simple and clean. He will also demonstrate techniques that you can use to make your automation code more maintainable. Finally, he will write code to implement these patterns taking them from theory to implementation.
by Esther Derby
Managers want teams to be empowered….but don’t want to give up decision making authority. Teams want empowerment, but may not know how to act on the power they already have. Executives want to drive engagement and action, but see only half-hearted compliance.
In all of these examples, power dynamics are at play. Words won’t matter until people acknowledge power. Once people acknowledge the fact of power, it's possible to look at how it is affecting people and actions. When we see power, we can see how power can make it harder–not easier–to achieve desired results.
In this session, we'll explore different definitions of power, where power comes from, and how people respond to power.
You will learn:
Two definitions of power, and how each affects leadership
Seven sources of power
How the use of power impacts peoples core concerns
How to boost creativity and productivity by addressing sources of power and core concerns
Agile principles and practices like individuals and interactions, limiting work-in-process, and continuous improvement are relatively simple to discuss but difficult to internalize and convert into value systems. Facilitated exercises and games that illustrate them can be used to drive home why they really matter. This session will combine the experience of participating in some key exercises, seeing firsthand how they run, and learning how to translate them into practical lessons on why Agile advocates certain values.
Traditional brainstorming methods can ruin your attempts at collaboration and engagement. In fact, decades of research has shown that traditional methods can actually be less collaborative, less engaging, and less creative than generating ideas individually and pooling them. However, the latest science behind brainstorming shows that our beloved post-it note can come to the rescue to increase the collaboration, engagement, and creativity of your team.
If you are already experienced in using silent brainstorming, this practical session will introduce you to the science and research to justify your approach. If you've never experienced silent brainstorming before, this session will give you something to try next week with your team that will help improve collaboration, engagement, and creativity. Regardless of your experience with silent brainstorming, you will learn how to integrate silent brainstorming into agile practices that you can use throughout the lifecycle of your projects and products.
We swim in a sea of language but seem to be drowning in misunderstanding.
Nowhere is this more apparent than in the efforts we make to change ways of organizing work in organizations.
Making common meaning of the language we use when working together takes conscious effort but we typically go about it unconsciously.
In this session we'll examine common patterns of unintended consequences that stem simply from the language we use to describe changes to the way we work. You'll leave with a new model for thinking about language and using it to better effect.
We'll discuss and practice the use of metaphor, mindset and specific practices to create shared understand in and between teams.
After this session participants willl be able to:
Avoid using language that undermines their goals
Recognize opportunities to make unspoken knowledge explicit
Choose the best communication options for different contexts
Hold conversations to clarify intended outcomes
Deceptively simple, incredibly powerful, this one simple trick is the closest thing to a cure-all for collaboration known to software development. Matt Heusser and David Hoppe will show you how, what it means, where to get started, and even work on a exercise that demonstrates the power of ... no, that would be telling.
Tired of working alone? Sick of the same partner? Be ashamed no more! Pairing promiscuity is one of the healthiest activities a team can employ. Pairing with many different people promotes knowledge transfer and understanding across the team. It's the most natural way of setting up teaching / learning environments to stimulate growth. Learn the business value of switching pair partners and how it can to provide project management flexibility and overcome the perils of "towers of knowledge."
More than just repairing frequently, learn how pairing works for many roles beyond the discipline of programming. It can work for designers, quality assurance and project management, too. Even more exciting is that it works cross functionally. Pairing a designer and programmer together can cause all sorts of new and fascinating avenues to explore.
This workshop will explore how successful pairing works across all roles as well as covering how to be properly promiscuous. The participants will actively engage in activities to discover the true power of pairing promiscuously and understands better how they can apply these processes to their own work environment.
Watch Dan Chuparkoff as he shares some of the secrets to kick-ass software development at Atlassian. He gives us a glimpse at a new Agile paradigm. Feedback cycles are short, code quality is awesome, and customers get the features they lust after. Hear how we use pull-requests for better code quality; collaborate fast to develop ideas; avoid meetings; tighten feedback loops to fail fast; shorten release cycles and work together happily from different corners of the globe. Sound like paradise? It is!
by Jeff Jakubiiak and Ed Neubecker
Bridging the gap from agile planning to continuous delivery with IBM Rational solutions
by Joe Vallone
It is no secret that when an organization chooses to transition to Agile methodologies, it requires an enormous commitment to leadership and change management. Even in prescriptive methods of Agile transitions, such as SAFe, I have found this subject matter deficient, especially in the area of practical application. This presentation is based on a training class I developed and conducted with executive leadership at American Airlines. It focuses on how to apply Dr. John Kotter's 8-step model of change management and leadership to help transition an organization to support an Agile transformation. I have been involved in large scale Agile Transformations at Nokia, AT&T, American Airlines, Telogical Systems and VCE. I have successfully applied the principles of this process at several companies, most recently at American Airlines IT division to train executives in Agile Change Management.
Dr. John Kotter is arguably the foremost authority on the subjects of Leadership and Change Management. He is a graduate of MIT and a professor emeritus at Harvard. Dr. Kotter's vast experience and knowledge on successful change and leadership have been proven time and again. The presentation was developed to apply the principles of Dr. Kotter's book: Our Iceberg is Melting, to Agile Organizational Change Management.
Technology is quickly moving to non-standard devices. Come learn what is possible in vehicles today from Tractors to Teslas.
We will discuss where things are headed and show some simple, yet fun "hacks" we have done with the Tesla Model S.
Using Rally's Software Development Performance Index, it is now possible to benchmark your Agile success using measures such as Responsiveness, Quality, Productivity, and Predictability. How does your Agile transformation stack up?
21st–22nd February 2014