5 Steps to Eliminate Database Change Risk in the Application Release Process
Posted by EdmontonPMAug 19
Live Webinar – August 27th, 2013 2:00 – 3:00 PM EDT
Duration: 1 Hours + QA – 1 Category C Self Directed Learning PDUs
Presented by: SD Times (Software Development Times)
Every time you move a database from development to production, change a production database, or update schema in an application, there’s a 78% probability your change will break the application or result in critical data loss.
Join Robert Reeves (LinkedIn profile) and Carey Benge (LinkedIn profile) as they share other surprising new research results from Simon Management Group on the true cost of Database change.
- They’ll lay out 5 steps to eliminate change risk in the application release process which are not being addressed by DBA tools.
- You’ll learn how you can eliminate manual scripting errors, break through costly database change bottlenecks which stifle complex application releases, increase release confidence, provide transparency to schema management and more.
No monotone speakers or boring slides here. These two industry veterans will cut to the chase and share their first-hand experiences with a game changing approach to Database Change and Configuration Management.
You will learn how to:
- Eliminate database change risk and bottlenecks in your develop-test-deploy process
- Accelerate releases, eliminate downtime and lower costs by automating deployment processes
- Reduce errors and know how changes will impact production environments – keeping application code, schema, people, and processes in sync
- Improve compliance with auto-documenting change management processes
- Increase quality of service with a holistic, repeatable, database-agnostic approach
NOTE : Attendees will receive the “Cost of Database Change†infographic containing Simon Management Group research results.
Who should attend: Many levels in your organization will benefit from this webcast including: DevOps, CTOs, VPs, directors and managers of application development, database developers , SCMs, IT and IT operations; release and middleware managers and application architects.
PDU Category C (PMBOK 5) documentation details:
Process Groups: Executing
Knowledge Areas: 8 – Quality 11 – Risk
- 8.1 Plan Quality
- 11.2 Identify Risks
- 11.5 Plan Risk Responses
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 5 Steps to Eliminate Database Change Risk in the Application Release Process
Leave a Reply