Design Thinking Approach for Analytics
•
1 like•1,087 views
Design Thinking Approach for Analytics by "Niyati Shah" from "BMC" . The presentation was done at #doppa17 DevOps++ Global Summit 2017. All the copyrights are reserved with the author
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to Design Thinking Approach for Analytics
Similar to Design Thinking Approach for Analytics (20)
More from Agile Testing Alliance
More from Agile Testing Alliance (20)
Recently uploaded
Recently uploaded (20)
Design Thinking Approach for Analytics
- 1. #DOPPA17 Design Thinking Approach for Analytics Niyati Shah 9th September 2017
- 2. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Agenda Define Analytics Business use of Analytics Case Study Approach for Analytics Development Design Thinking Approach Benefits of Design Thinking Approach Summary
- 3. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) What is Analytics? Analytics is the process of : Information Discovery Interpretation Communication of meaningful patterns in data Arriving Business Decisions The fastest way to find a needle in the haystack is to reduce the size of the haystack.
- 4. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Business Use of Analytics
- 5. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Analytics Development - How it is Different
- 6. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Analytics use case Fraud Detection o Track user login o Identify the pattern o Based on outlier/spike identify malicious login/activity
- 7. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Failed user Login – Data Set Time No of Failed Login Attempts Standard Deviation Percentile Hour 1 10 - - Hour 2 14 12 10 Hour 3 12 12 12 Hour 4 15 12.75 12 Hour 5 20 14.2 14 Hour 6 500 95 15 Hour 7 80 93 15
- 8. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Flow for Analytics Development
- 9. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Design Thinking Core Desirability ,Feasibility, Viability
- 10. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) ‘Design Thinking’ Approach Think Big, Act Small, Fail Fast, Learn from End user and Refine
- 11. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Benefits of ‘Design Thinking’ Approach
- 12. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
- 13. #DOPPA17 As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us) Q & A Reach me@ niyati.shah27@gmail.com https://www.linkedin.com/in/niyati-shah-1028a51b/
Editor's Notes
- raw data-> information -> pattern
- Data Valocity, Variety, Volume, value
- Empathise: Understand the problem by discussing it with experts, get understanding of environment, this will make sure, individual assumptions are kept aside. Define: Define the problem statement. Ideate: How the problem will be solved. To identify new solutions to the problem statement you’ve created, and you can start to look for alternative ways of viewing the problem. Prototype:The solutions are implemented within the prototypes and, one-by-one, they are investigated and either accepted, improved and re-examined, or rejected on the basis of the users’ experiences Test:the results generated during the testing phase are often used to redefine one or more problems and inform the understanding of the users, the conditions of use, how people think, behave, and feel, and to empathise. Even during this phase, alterations and refinements are made in order to rule out problem solutions and derive as deep an understanding of the product and its users as possible.
- Using governance and automation techniques to optimise collaboration across development and operations to enable faster, more predictable and more frequent deployments to market”.
- From a cultural perspective these methods are meant to bring the customer or business stakeholder closer to the IT organisation through closer collaboration and by making delivery less black box and more white box.