diff --git a/misc/SoftwareDevelopmentProcess.md b/misc/SoftwareDevelopmentProcess.md
index 0ede001151..23d3341d84 100644
--- a/misc/SoftwareDevelopmentProcess.md
+++ b/misc/SoftwareDevelopmentProcess.md
@@ -7,6 +7,8 @@ By default, each Pull Request is expected to be complete and expected to not bre
 If a Pull Request is a work-in-progress or draft or not intended for merge yet, it should be clearly marked with "[WIP]" prefix in the title.
 
 Pull Requests which are not complete, not marked WIP or fail gate check should be closed to reduce a chance of confusion.
+It is usually helpful to discuss proposed changes prior to Pull Requests - we have Slack to collaborate and coordinate so let's use!
+
 
 
 TODO: we have an urgent need to make gate check more reliable & expand what's included into gate check
@@ -15,3 +17,4 @@ The primary hardware platform for rusEfi is stm32f4 - as of November 2019, only
 
     
 
+See also [Functional tests CI info](jenkins\functional_test_and_build_bundle\readme.md)
\ No newline at end of file
diff --git a/misc/jenkins/functional_test_and_build_bundle/readme.md b/misc/jenkins/functional_test_and_build_bundle/readme.md
index b8d27c4366..5598a6efea 100644
--- a/misc/jenkins/functional_test_and_build_bundle/readme.md
+++ b/misc/jenkins/functional_test_and_build_bundle/readme.md
@@ -1,3 +1,8 @@
 
+This configuration
+1) builds bootloader from firmware/bootload just to validate that it builds (TODO: extract to separate job?)
+1) compiles two versions of F4 version of firmware - with and without asserts, _fast_ and _debug_.
+1) flashes _debug_ version of F4 into stm32f4discovery and runs a suite of tests against it. The source code
+of tests is embedded into rusEfi console by the way (TODO: nicer UI for console to test F4 outside of Jenkins?)
 
 ```misc/jenkins/functional_test_and_build_bundle/run.bat```
\ No newline at end of file