Week 2: Presentation proposal (lvainio & oscols) #2378
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Split.io, a Feature Flag tool, that can be used for A/B Testing
Names and KTH ID
Deadline
Category
Description
This presentation will start off by introducing Split and how it's relevant to this course, followed by what A/B testing is.
We will show code snippets on how the feature flags are implemented in production code and how it can be used for A/B testing.
Relevance
Split is a useful tool for creating and managing feature flags for applications. This tool also allows different roll out methods to be implemented such as A/B testing. This technique is useful for the continuous delivery part of DevOps.
In devops, A/B testing is a method that can be used to compare different versions of the same application based on usage data of specific user groups. Based on the data, the team can go ahead and make more informed decisions on which features to implement. This allows for fast feedback and decisions can be made from data and not just individual opinions.