Conversation-driven Development: ChatOps and White-box Processes

Transcription

1 Conversation-driven Development: ChatOps and White-box Processes Janos Koppany CEO, Intland Software 3/8/2018

2 What we do

3 Intland Software s ALM and DevOps ALM: lifecycle management with traceability and compliance DevOps: align teams and stakeholders, enhance collaboration, integrate feedback, automate the CI&CD pipeline Requirements Management a key component in both 3

4 Key Industry sectors Automotive, Medical, Aviation, Pharma Medical Device Medical Device Development Development Automotive Embedded Systems Development Software Development in the Aviation, Aerospace, & Defense Industries Pharmaceutical Project Management Comply with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC and more. Reduce development time and costs. Enforce the use of mature processes to achieve compliance with ISO 26262, IEC Automotive SPICE, CMMI and more. Develop safe and reliable airborne equipment. Comply with RTCA DO-178C and DO-254. Comply with Good Automated Manufacturing Practice guidelines along the pharma production lifecycle. 4

5 Challenges of collaboration Accelerating Agile, DevOps development cycles: collaboration and alignment are vital Integrated view of the lifecycle from RM to QA, Compliance, Ops Intra-team and inter-team collaboration Transparency & alignment in suppliers relations gaining importance Traceability for compliance is key 5

6 Challenges faced in 2017 Too many notification s cluttering our inbox, limited transparency Difficult to find information (dev, support, marketing, sales, finance working together) Integrations between tools and departments too clunky need for a simple, quick solution Mobile access Need for channel/context-driven chat Boots for simple integrations i.e. PLM, AI 6

7 New phenomena in development ChatOps conversation-driven development: borrowed from GitHub (Hubot) Market trends: Slack, Google, Facebook, Microsoft, Atlassian releases new chat products Amazon to buy Slack? Salesforce making Quip & other acquisitions FB Messenger (900M users) to integrate bots, plan for AI integration Players on the market: Slack Mattermost MS Team HipChat 7

8 Goal Give the Development team the freedom to find or create a solution for their needs Traceability across tools and teams Accelerate and simplify intra-team & inter-team collaboration and transparency Constraints for the development team: Slack is preferred, the solution must be portable to Mattermost Group/team channel communication, person-to-person chat Use bots to integrate with other systems e.g. AI, PLM, etc 100% traceability 8

9 Result: ChatOps Conversation-driven development with mobile-ready ChatOps Accelerate enterprise teamwork Integrate chat and development Access lifecycle data, and manage ALM artifacts with simple chat commands Use bots in your conversations to automate tasks 9

10 Intland s Chatbot Conversation-driven development with responsive UI Chat conversation traceability to all other artifacts Access lifecycle data and manage RM, DEV, TEST artifacts with simple chat commands in a traceable manner Use bots in your conversations to automate tasks Run build, shows build pipelines, run deployments Show log information and Monitor general application health 10

11 11 ChatOps & DevOps integrations

12 White box / Black box Collaboration across team, tool, company boundaries Software content increasing in supplier-provided product components Need for traceability, collaboration, transparency to expand across company boundaries Enhanced supplier relations via white-box development 12

13 Result: White-box Development concept Term borrowed from white-box testing: opening the hood (internal framework, components, and processes) Enhance supplier integration Complete transparency throughout the development of a component by a supplier Improved product quality, standards compliance, and collaboration 13

14 Outlook DevOps + white-box development with value stream-wide traceability & compliance + 14

15 15 Examples Continuous Integration Jenkins pipelines

16 16 Examples Operation s communication