Articles on abc.net and elsewhere reported that Volvo has recently discovered a non-traditional requirement: Any self-driving vehicle approved for use outside Australian cities must recognize kangaroos on or near the roadway and take proper actions. The kangaroo’s bounce confused the large animal detector! In this session, industry expert David Gelperin shares a new perspective on the value of imprecise requirements and explores the nature of testing them. Excess precision may hamper the development of optimal solutions by excluding effective designs. Imprecise statements reduce the risk of excess precision and signal the need for analysis to understand their deeper meaning. Intentionally imprecise requirements entail a mixture of research and development and are a valuable supplement to traditional requirements.
API-based applications have become ubiquitous in the past few years. Yet many of us still really don't know what an API is from the inside out. Moreover, many of us don't know much about how to comprehensively test them! Join Paul Merrill to learn what everyone is doing and talking about, related to APIs: microservices, REST, endpoints, requests, request methods, and responses. Paul demonstrates four free tools you can use to directly interact with a simple API: curl, the browser, Postman, and Java (with Rest Assured). Learn techniques for testing APIs at the service level and how to test APIs faster with greater coverage and quicker test automation. Walk away with an understanding of what JSON is, how APIs use JSON, and how to go about verifying that it is correct. With new knowledge and skills, you’ll do a better testing job and give more valuable feedback to the API designers and developers.
Organizations undergoing a digital transformation must adopt new and meaningful ways of working. For a successful transformation, in addition to agile processes, teams must also leverage agile engineering techniques and models. Continuous focus on agile engineering principles will provide a solid ground for teams to enhance their agility and deliver better software, faster.
How you think about software design can have a big impact on how effective you are when you do it. All of us have different criteria for success, and some of them aren’t even conscious. We have to figure out what resonates for us so that we make the right choices, and we can get a clue about the right choices for us by looking at the metaphors we use when we talk about software.
In agile, everything we do is an experiment. Product development is no different. We think we know what the customer wants, and the customer thinks they know what they want, but it turns out we're all wrong! To get to validated discoveries about our features, we must understand how to write a better hypothesis for our development experiments. This session focuses on challenging the mindset that we are validating options during our experiments. Natalie Warnert will show you how to eliminate options that don't work with data and feedback by looking at your product hypotheses as tests that cannot be proven. This way of testing your product design preserves options and helps to eliminate choosing the wrong thing because of your confirmation and customer biases. Natalie will present key metrics you can use to help guide your experiments and practical ways to look at your ideas as something to test, rather than validate.
Do your Retrospectives feel like a repeat of the last one? Are they moan and groan sessions? Want to try something new to give your team a boost? When design principles are applied to strategy and innovation, the success rate for innovation dramatically improves. Great design has that “wow” factor that makes products more desirable and services more appealing to users. Why not try using known design principles during your retrospectives to get that "wow" factor for your teams! In this session Catherine Louis will provide a Design Thinking overview. You’ll roll up your sleeves up and try it. You will learn how to Empathize with your team's issues, how to Define a point of view, construct a challenge, Ideate towards Prototyping and Test a retrospective solution. We will move from problem space to prototyping in one super-duper hands-on Design Thinking retro session.
Many IT managers find themselves banging their heads against a wall trying to get upper management to invest in DevOps. Managers see clear opportunities to implement it into their organizations but get a No from senior executives. Many managers are frustrated that, despite all the...
You’re a professional project manager or ScrumMaster. Your software development projects never fail because you follow all the best practices. Right? We all know better. Unfortunately, many projects fail, and they fail due to issues outside the team's control. The reality is that we need...
As companies realize the need for rapid application development, they are embracing DevOps methodologies. But implementing DevOps practices without establishing a culture of quality often results in lower quality software or a poor customer experience, which impacts the business bottom line.
Building an app for a single platform is difficult, but designing, implementing, and testing an app targeting multiple operating system platforms can be next to impossible. The secret balances upfront design with customer feedback.