|
|
|
|
|
|
See Sessions From:
Wednesday
|
Thursday
BW1
Projects & Teams
Context-driven Leadership: How to Ride a Bull through a China Shop
Kent McDonald, Knowledge Bridge Partners
Software development projects are just different. They’re often high-risk ventures with extremely complex interrelationships, filled with uncertainties, dependent on scarce knowledge workers, and much more. So, the leadership style and skills needed to be successful are quite different from those needed in simple, stable projects that run through organizations. Kent McDonald introduces his Context Leadership Model, an important managers’ tool that uses the project characteristics of uncertainty and complexity to provide guidance for project leadership and governance. Kent demonstrates how to assess the characteristics of a project, how to choose the project leadership approach based on those characteristics, and how to tailor it for unique situations. Work with Kent and your peers to evaluate the characteristics of your own projects, identify the best leadership approaches, and find out what you need to do to prepare yourself to ride a bull of a project safely through a china shop.
Learn more about
Kent McDonald
BW2
Business Analysis & Requirements
EARS: The Easy Approach to Requirements Syntax
John Terzakis, Intel
One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides examples of typical requirements and explains how to improve them using the Easy Approach to Requirements Syntax (EARS). EARS provides a simple yet powerful method of capturing the nuances of functional requirements. John explains that you need to identify two distinct types of requirements. Ubiquitous requirements state a fundamental property of the software that always occurs; non-ubiquitous requirements depend on the occurrence of an event, error condition, state, or option. Learn and practice identifying the correct requirements type and restating those requirements with the corresponding syntax. Join John to find out what’s wrong with the requirements statement—“The software shall warn of low battery”—and how to fix it.
Learn more about
John Terzakis
BW3
Cloud Computing
Cloud Computing 101: Concepts, Benefits, Challenges, and Costs
Arlene Minkiewicz, PRICE Systems, LLC
Cloud computing is a paradigm that makes the notion of utility computing a reality. Instead of investing scarce capital in computing resources, IT organizations are turning to pay-for-use hardware, software, and infrastructure available through the Internet. Unfortunately, because cloud services vendors have their marketing engines further into the cloud than their technology actually reaches, there is a great deal of hype around cloud computing. Arlene Minkiewicz introduces the concepts of cloud computing, discusses the different kinds of clouds, and explores different models for employing cloud-based services. She provides insights into the benefits, challenges, and risks associated with moving development, testing, and production systems to the cloud. Explore the costs you’ll face to migrate to cloud computing and how to estimate the on-going costs associated with the utility computing model. Strip away the hype and leave with a solid foundation of what the cloud is all about and where it’s headed.
Learn more about
Arlene Minkiewicz
BW4
Going Mobile
Mobile Apps: Breaking Down the Barriers
Todd DeCapua, Shunra
Mobile application development introduces additional complexity when compared to building traditional applications. In order to successfully develop and deploy mobile applications, it is essential to account for variability in networks, service providers, devices, operating systems, and browsers. Todd DeCapua shares practices for successfully navigating this complexity while preserving both speed-to-market and application performance. Outlining a new approach to the agile development-test-deploy cycle for mobile, Todd demonstrates how to integrate functional testing and performance engineering throughout the application lifecycle and establish a new level of cooperation among test, development, and operations. With Todd’s guidance, you will learn how to empower change in your organization and provide a strategic roadmap for your business to speed mobile application development while improving application quality and the end user experience. Using real-world examples from organizations that have broken down traditional barriers, Todd shares practical lessons that you can apply immediately to your development practices.
Learn more about
Todd DeCapua
BW5
Projects & Teams
Seven Habits of Highly Successful Project Managers
Ken Whitaker, Leading Software Maniacs
It is easy to find a million ways that software development and project managers can let down their teams and their projects. Ken Whitaker has identified seven pragmatic leadership tips and techniques you can use to build and sustain a great team that consistently delivers great software. Specifically, Ken discusses how to keep project management jargon and bureaucracy to a minimum, what your role as a project manager really is, how to take action to lead rather than just manage, how to mitigate losing your best performers to competitors, how to design in quality from project inception, how to realistically set schedule expectations, and some great ways for simplifying your communication to stakeholders. You'll find this presentation to be useful, exciting, and motivating. These habits are powerful—yet so simple you can put them into practice immediately.
Learn more about
Ken Whitaker
BW6
Business Analysis & Requirements
Ten Tips to Get Requirements Right and Make Stakeholders Happy
Carol Askew, Intermountain Healthcare
Have you ever delivered an application with functionality that was not what the stakeholders really wanted—or needed? Have you ever discovered that you were listening to the wrong people? Has your team ever developed a really beautiful application that no one uses? A truly successful project delivers what is most important to the business, the sponsor, and the key stakeholders. Carol Askew shares ten requirement-related tips she uses at her large healthcare organization. For example, to keep her projects on track, Carol developed specific requirements checkpoints to review throughout the software development lifecycle. She describes what to look for in project initiation documents, requirements elicitation sessions, user stories, scope issues, and project schedules. Take back ideas that you can use right away to help achieve success in your own projects. Although you probably won’t save the world, you will end up with very happy customers!
Learn more about
Carol Askew
BW7
Cloud Computing
Leaping into the Cloud: Risks and Mitigation Strategies
Seth Eliot, Microsoft
Ken Johnston, Microsoft
The cloud has rapidly gone from “that thing I should know something about” to the “centerpiece of our five-year corporate IT strategy.” However, cloud computing is still in its infancy. The marketing materials ignore or gloss over the many risks present today in the cloud—data loss, security leaks, gaps in availability, migration costs, and more. Ken Johnston and Seth Eliot share new research on the successful migrations of corporate IT and web-based companies to the cloud. They lay out the risks to consider and explore the rewards the cloud has to offer when companies employ sound architecture and design approaches. Discover the foibles of poor architecture and design and how to mitigate these challenges through a novel Test Oriented Architecture (TOA) framework. Take back insights from industry leaders—Microsoft, Amazon, Facebook, and Netflix—that have jumped into the cloud so your organization does not slam to the ground when it takes the leap.
Learn more about
Seth Eliot,
Ken Johnston
BW8
Going Mobile
Selecting the Right Mobile Testing Solution: Practical Considerations and Proven Practices
Eran Yaniv, Perfecto Mobile
Because the mobile market is extremely dynamic, maintaining consistent application quality is always difficult. Managing the risk exposures with mobile apps and embedded software requires comprehensive testing of a wide variety of platforms operating on multiple networks. Testers have to contend with short development cycles that require continuous QA efforts. Three key building blocks are required to overcome these obstacles: device-agnostic automation, access to a large selection of handsets and tablets, and ways to seamlessly apply your existing testing tools, skills, and knowledge to mobile. From his experience working with enterprises going mobile, Eran Yaniv shares the do's and don'ts for selecting an enterprise-grade mobile testing and automation platform, and offers his analysis of the advantages and disadvantages of the various approaches. Eran covers key considerations for developing your mobile testing framework, leveraging existing test tools for mobile testing, deploying a robust mobile automation strategy, and more.
Learn more about
Eran Yaniv
BW9
Projects & Teams
When the Pressure Is On: A Risk-based Approach to Project Management
Reán Young, The Kroger Company
Teams everywhere have experienced tight deadlines for software development projects. In such time-constrained situations, how can you systematically determine where to focus the team’s efforts? How do you determine the right level of requirements documentation? How do you decide how much testing will be necessary so that you are not doing too little—or too much? Reán Young shows how a risk-based approach to these and many other issues helps you identify project strategy options and set priorities. Based on a combination of business and technical factors, you’ll learn to evaluate risks in each area of the application, and devise a plan to ensure that the most critical features will be developed, tested, and delivered before the deadline. When the pressure is on, project teams will be equipped to take ownership of the process and have the tools needed to target, prioritize, and focus appropriately on all aspects of the project—requirements, development, test, and release.
Learn more about
Reán Young
BW10
Business Analysis & Requirements
How to Rework Poorly Defined Requirements
Steve Caseley, CBT Nuggets
Poorly defined requirements are even more dangerous than no requirements because they offer the illusion that all is well during development. However, when user acceptance testing begins, requirements problems surface and the users rightly say, “I don’t care that the system test has passed, this isn’t what we need, and we won’t be signing off.” Steve Caseley reviews the actions he took to rework the requirements on two failed projects and the changes he made to get new projects off to the right start. Steve explores how statements such as “new reports must be balanced with the old reports” were re-written to identify quantifiable variances. He shows how other loosely defined requirements were reworked to provide clear mapping of measurable requirements to expected test results. Join Steve to gain knowledge and insight you need to refactor poor requirements—and to develop the requirements your team and customers need on your next project.
Learn more about
Steve Caseley
BW11
Cloud Computing
ALM in the Cloud: Bringing Code to the Cloud and Back Again
Mik Kersten, Tasktop Technologies
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. See what business and development managers must wrap their heads around with an ever-growing set of shiny—but often siloed—tools that are wreaking havoc with governance. Leave with a new appreciation for and understanding of what it takes to develop mission-critical systems for the cloud.
Learn more about
Mik Kersten
BW12
Software Quality
Developer-driven Quality: Putting Developers in the Drivers’ Seat
Colby Litnak, MasterControl, Inc.
Although many software development teams rely on their QA/Test departments to uncover critical product defects near the end of development, we all recognize the inefficiency of this approach. It’s better to find and fix defects earlier in the software development process to save time and money in the long run! Colby Litnak explores key concepts that encourage and empower developers to take primary responsibility for producing quality software. As with a souped-up race car, developers need specially designed tools and practices when they are at the wheel: fail-fast frameworks, one-click test execution, automated defect prevention principles, automatic notifications of untested code, hurtful test failures, and much more. Discover the principles developers must embrace to produce high quality code the first time—before it goes to QA/Test. If you are ready to get in the fast lane and put your developers in charge of quality, this session is for you.
Learn more about
Colby Litnak
Top of Page
|
|
|
 |
| | | |
