Live Webinar August 4th, 2016, 2:00 pm – 3:00 pm EDT
Duration:1 hour Webcast Up to 1 Category C PDU – Free PDU
Hosted By:  StickyMinds/Techwell

Whether you call it your “definition of done,” “list of constraints,” “global acceptance criteria,” or something else entirely, many agile teams rely on a documented, shared understanding of when a user story is complete. Oddly, performance testing is rarely mentioned.

Performance is becoming a crucial part of user experience, and user experience is becoming an integral part of development.

It’s no longer an option to produce user stories for web and mobile apps where “working code” only works when the application isn’t under load.

Join this web seminar to learn tried-and-true practices for testing performance without slowing down agile development. You’ll learn:

Advantages of using “definition of done” for performance instead of non-functional stories:

• How to add performance testing to your “definition of done”
• When completed user stories can skip performance testing
• How to automate performance testing to keep pace with development

Presenters:

Steve Weisfeldt (LinkedIn profile) Senior Performance Engineer Neotys; is a provider of load testing software for web applications. Having been in the load/performance testing space since 1999, Steve is an expert at enabling organizations to optimize their abilities to develop, test, and launch high-quality applications efficiently, on time, and on budget. Prior to Neotys, Steve was president of Engine 1 Consulting, a services firm specializing in all facets of test automation.

Tim Hinds (LinkedIn profile) Director of Product Marketing Neotys; has a background in agile software development, Scrum, kanban, continuous integration, continuous delivery, and continuous testing practices. Previously, Tim was product marketing manager at AccuRev, where he worked with software configuration management, issue tracking, agile project management, continuous integration, workflow automation, and distributed version control systems.

PDU Category C (PMBOK 5) documentation details:
Process Groups: Planning Executing
Knowledge Areas: 4 – Integration 5 – Scope 6 – Time

• 4.3 Direct and Manage Project Work
• 5.1 Plan Scope Management
• 5.2 Collect Requirements
• 5.3 Define Scope

As a Category C, ‘Self Directed Learning’, activity remember to document your learning experience and its relationship to project management for your ‘PDU Audit Trail Folder.’

Click to register for:
Agile Teams Need Performance Testing
In Their Definition Of Done