Kitfox - Scope
This document represents the preliminary scope of the work for the Kitfox team
Scope categorized by topics and prioritized:
Priority | Topic | Description | Responsible person/s |
|---|---|---|---|
0 | Support | Daily tasks and activities with a focus on support of development teams. | @Dmytro @Arsen Atoyan |
1 | Jenkins upgrade | Set of tasks with a focus on Jenkins upgrades and improving build processes with the usage of dynamic K8S agents. | @oleksandr_haimanov (Unlicensed) @Vasyl Avramenko |
2 | Shift-left strategy | Scope related to the implementation of the shift-left testing strategy | @oleksandr_haimanov (Unlicensed) |
2 | Eureka | Scope for implementation of Eureka functionality on Rancher(dev) environments | @Eldiiar Duishenaliev @Yaroslav Ishchenko |
3 | Kafka TLS endpoints (?) | Related info has been shared with requestor. | |
4 | Pipelines improvements and stabilisation | Scope (placeholder) for ongoing tasks with a focus on Jenkins pipelines improvements and stabilisation |
|
5 | Infrastructure improvements/updates | Scope for tasks related to Infrastructure components upgrades and improvements/optimizations | |
6 | DB backup/restore automation | Scope for automation of DB backup/restore on Rancher environments |
|
6 | Logging | Scope for Logging feature on Rancher environments |
|
6 | Monitoring | Scope for Monitoring feature on Rancher environments |
|
Hello,
I’m not agree with scoping approach above.
Since Eureka will become a primary deployment approach each and every team member should be capable to work with it.
Support scope is a kind another limitation. Meaning person(s) will not be involved in various of activities. Additionally thinking of BCP(business continuity plan), if as an example me(Eldiiar D.) got sick or anything else happens, someone should cover the area I’ll be looking after, imagine if 2nd person is out of office at the same time, then entire stream will be blocked.
Just thinking out loud…