4. A way to develop software that emphasizes communication, collaboration, and integration between development and IT operations teams.

5. With different toolsets, information needs, and workflow processes, communication, collaboration, and integration between development and IT operations teams can be a challenge.

6. Application lifecycle – common challenges Develop Rapid reaction to feedback Operate Software to value delivery Development & testing Operations Problem assigned to engineering Ops backlog Monitor Fix Working software No actionable feedback resulting in high MTTR Isolated operations tools and workflows Long deployment cycle times Users find defects in production Production incidents are hard to debug Unable to reproduce error in development environment

7. Dev and IT operations have different goals Development Driven by needs for frequent delivery of new features IT Operations Focus on availability, stability, and cost efficiency Different goals → gap that impacts business value

8. Loss of efficiency Takes longer to clearly communicate and track complex issues across teams Reduced agility Slows application production and deployment Increases production risk with frequent changes Organization can’t respond to market opportunities Customer dissatisfaction Takes longer to get new releases and fixes to customers

9. Streamline communications between Dev and IT Ops teams Integrate IT and Dev tools and workflows for greater efficiency Quickly detect and fix problems that need help from Dev team Decrease the time it takes for application maintenance and delivery into production Optimize for a fast-moving service environment Extensible – Use Orchestrator to automate processes

12. Alert in Operations Manager Enabled alert attachments and synchronized alerts with TFS work items Attach IntelliTrace snapshot Assign alert to Engineering Developer gets associated TFS Work Item with IntelliTrace snapshot Development tracks and fixes problem, changes work item status Operations Manager alert status changes and IT can close the alert

13. Shared artifacts Output of operational process is natively consumed by Dev tools and vice versa Operations Manager in System Center 2012 can collect root cause data in IntelliTrace format Common goals IT and Dev have common MTTR metrics Operational alerts can be escalated from Operations Manager directly to TFS as Operational Issue work items Results Collaborative culture where stakeholders work together across the application lifecycle

36. IT Ops knows issue status by checking the Operations console Developers use own work environment to view and track issues Developers can request additional information from IT Ops Enables deep troubleshooting Gives developers the detailed information to find and fix problem code

38. Alert Attachment Management Pack TFS Work Item Synchronization Management Pack IntelliTrace Profiling Management Pack Global Service Monitor management packs Microsoft Visual Studio 2012 Team Foundation Server Monitoring Management Pack

39. Gives you: Ability to attach files to Operations Manager alerts Defines task: Open Alert Attachment Location for each alert Why it’s needed: Required for Global Service Monitor and IntelliTrace Can be used by other management packs, need authoring skills Key configurations: Allocate space on the file share Set override to define where you want to store the files Configure a Run As profile with an account that has permissions to access the file share location How to Configure File Attachments for Operations Manager Alerts in System Center 2012 SP1 Enable the Alert Attachment discovery rule and point to the Alert Attachment file share location

40. Gives you: Ability to Synchronize Operations Manager alerts with TFS work items You can also: Change the frequency of synchronization with TFS Get notifications when development reassigns work items or needs more information Automatically close alerts when work items are resolved Stop and resume synchronization Automatically send attachments for specific apps or all apps to TFS (auto assign to engineering) Choose which project collection and which area in TFS is used for each app component How to Configure Integration with TFS in System Center 2012 SP1 “The heart of DevOps”

41. Gives you: Ability to send developers exact information about the code problem in detailed log files You can also: Import from the System Center 2012 SP1 media Automatically attach APM event IntelliTrace snapshots Collect full IntelliTrace snapshots – must have this MP How to Configure Integration with IntelliTrace Historical Profiling IntelliTrace log files give devs the details

42. Gives you: Ability to monitor externally–facing websites and web services from locations around the world Ability to view GSM web test results and assign alert to Dev using TFS synchronization Link to the session: http://channel9.msdn.com/Events/MMS/2013/AM-B303

43. Gives you: Real-time visibility into the health of the developer TFS environment You can also: Monitor TFS components, such as application tier server instances, team project collections, build servers, and proxy servers Get it on the Microsoft Download Center

44. System Center Operations Manager + DevOps Management Packs + Visual Studio and Team Foundation Server (TFS) + IntelliTrace and Application Performance Monitoring (APM) + Global Service Monitor A platform to build collaborative DevOps processes

46. Review compliance on sharing production data What are the SLAs? How technical is your IT Ops team? How agile is the application lifecycle? Are your web applications accessible from the Internet?

50. Complete your session evaluations today and enter to win prizes daily. Provide your feedback at a CommNet kiosk or log on at www.2013mms.com. Upon submission you will receive instant notification if you have won a prize. Prize pickup is at the Information Desk located in Attendee Services in the Mandalay Bay Foyer. Entry details can be found on the MMS website.

51. Resources