Every day more agile practices and styles emerge, overlap, and compete. This proliferation challenges you to choose from among XP, Scrum, lean, Kanban, or the ways of the emerging Lean Start Up crowd. Rather than stumbling down one path or another, join David Hussman as he shares tools for assessing and designing an agile process with practices that address your specific needs and constraints. David starts by teaching a simple assessment process to help you understand where you are today. Then, he offers ideas for selecting a meaningful set of practices and moves on to teach you how to create a meaningful and measurable coaching plan. David covers the selection of product planning tools, iterative delivery tools, tracking tools, and more. If you want to clear the fog about which agile practice will really help you, come for some answers. Even if you don’t yet know what questions to ask, David can help.
You’re familiar with agile and perhaps practicing Scrum. Now, you want to learn about Kanban to see if it is something to add to your development toolkit. Can Kanban help you? How does it differ from Scrum and other agile methodologies? Kanban is quickly being adopted by teams that want to improve their productivity. Kanban focuses on continuous flow and incorporating the theory of constraints which together allow teams to improve and streamline their product delivery. Learn about Kanban-not only the theory, but also practical lessons on transitioning your team to Kanban. Get insight into moving from Scrum to Kanban and pick up techniques that can aid any team. See cumulative flow diagrams, WIP (work-in-progress) limits, classes of services in action, and hear about other ideas from the Kanban toolset. Come and grow your agile repertoire!
While Scrum and XP have become very popular in agile development shops, most companies adopting them run into problems beyond just a few teams. These challenges often fall into a common set of patterns, which points to a lack of systems thinking-the process of understanding how things influence one another within a larger whole. Alan Shalloway shares his ideas on how the agile community can move beyond its team-centric approach to adopt a more holistic, systems-based approach. Systems thinking creates new opportunities to create substantially larger development teams-Alan calls them “pan-teams.” These teams work interdependently with a common vision and context. Pan-teams enhance the motivations for the teams and individuals to collaborate as a normal part of their daily work thus reducing the amount of forced collaboration.
In a world where technology is rapidly changing, development practices are quickly evolving, and teams are frequently reorganized, how can you remain steady and true to yourself? Even though things are changing around you, you can build a solid framework of personal beliefs to guide you throughout your professional career. To develop a credo-from the Latin “I believe”-is to take a personal journey through your professional life and the ideas that shaped it, ultimately creating your own statement of core beliefs. This credo forms a stable foundation for personal plans and actions. Marlena Compton shares the framework she’s used to build her professional credo. She examines manifestos and mission statements that have influenced her beliefs about building software and how she uses her credo as a basis to form concrete goals and take action.
By next year, 90 percent of large enterprises will include open-source software as business critical elements of their IT portfolios. However, most software development organizations have limited capability to govern the process of selecting, managing, and distributing open-source components-leaving them exposed to unforeseen technical and compliance risks. Larry Roshfeld examines how open-source components-and their dependencies-may expose your company to unforeseen and unnecessary vulnerabilities. He outlines the significant threats to software quality, stability, performance, security, and intellectual property that have occurred using such components. Then, Larry shares an action plan for balancing the risk/reward trade-offs of open-source software in the enterprise. Find out how to ensure that your organization uses only the highest quality open-source components and avoids the common vulnerabilities.
Speedy delivery is almost always a primary project goal or a significant project constraint. To shorten project duration without sacrificing quality or budget, you need to know where to focus the team’s efforts. Mining the QSM database containing many quantitative metrics and numerous qualitative attributes, Paul Below shares the factors that have the greatest influence on project duration. While he’s at it, Paul debunks a couple of myths. For example, many managers consider team skill to be important in determining duration of software projects-not so. The most important factors are certain types of tooling, architecture, testing efficiency, and management/leadership skills, which Paul explores in depth. Learn a technique for normalizing your projects for size by computing the standardized residual of duration.
All of us have experienced situations when we receive feedback. Some we readily accept; some we quickly reject. In a community that should be dedicated to constantly inspecting and adapting, why do we reject some feedback immediately? Tricia Broderick believes that self-reflection is the key to processing feedback in a positive light. In this interactive session, you’ll work with Tricia and other delegates to experience enriching discomfort, practice deep reflection, and ascertain why we can be so quick to dismiss feedback. Gain an understanding of how discomfort and self-reflection can be an IT professional's best friends. Leave with an expanded understanding of self-reflection that includes taking greater responsibility for personal development and tweaking your improvement-seeking process. If you are looking to get out of your comfort zone and grow as an individual and team member, this session is for you.
More than 70 percent of new software products fail or perform below expectations. Achieving product-market fit is essential-and doing it quickly and within budget increases your chances of success. However, the methods you should use depend on the problems you are trying to solve. The predominant phase-gate model used today is not always the right choice or fastest path to market. As an alternative, lean product management approaches focus attention on applying the right process at the project level. Greg Cohen describes the four product-market fit challenge types, how to identify the challenge type your project faces, and how to adjust your process accordingly.
Just as John Steinbeck was able to identify the complex system of tides, eddies, and other currents that bring nutrients to support life in the Pacific Ocean, you need to do the same for the complex human system that builds software products. Ray Arell argues that development productivity can increase only when you enable developers to grow and master the craftsmanship around their work. Describing a systems model of software productivity, Ray explores the elements necessary to “feed” the system and achieve the highest potential productivity. To help you diagnose systems issues, Ray demonstrates a visual tool-casual loop diagrams-that shows you how to identify and address the impediments that slow teams and degrade job satisfaction. He uses the same tool to show how agile and lean methods establish key reinforcing loops that improve productivity.
The deployment destination for today’s applications is going through its biggest transition since the rise of the application server. Platform-as-a-Service (PaaS) and other cloud service offerings are putting pressure on every stakeholder in the application lifecycle, forcing us to modernize both our skill sets and tool stacks. Mik Kersten describes the key cloud technology trends and demonstrates how the coming wave of cloud-friendly application lifecycle management (ALM) tools and practices will become the defining factor for productivity and ultimate success. Discover the new challenges developers face when deploying and debugging multi-tenanted applications on hosted infrastructures. Learn how continuous integration loops require testers to learn new tools that connect them directly to running applications.