Mr Bartlett Blogs
  • Ramblings...
  • OLD_CEFKorg
    • New CEFKorg Page!
    • About Computer Equipment For Kids
    • Alliance of Awesomeness
    • How do I help?
    • The Places We've Been
    • Tutorials
    • Learning Sites
    • Conferences

Communications

8/4/2017

0 Comments

 
If you have poor collaboration tools and/or folks don’t know how to use them you will be in trouble.   Defining what tool is used and when seems like a silly task but it will save you a lot of heartache in the long run. 

Slack
If you use Slack each channel should have a designated use and the team should know when slack is the appropriate medium vs something like email or documenting in confluence.  Here are a couple of channel examples with 'use definition': 
  • JIRA - Any update to an issue (added, modified, comments)
  • Confluence - Any update to a space/page (add, modified, comments)
  • Bitbucket - Any update to Pull requests (add, modified, comments)
  • Develop - Any update related to the actual development work or questions
  • Process - Any update about the overall development process or changes to the process
One area to think about when creating channels in Slack is will the channels defined be granular enough to make sense if multiple projects are using this integration?  If we have project A and project Z and they are both utilizing the existing channels will the messages confuse other teams?  Should we create specific channels for each project?  Project A - Jira, Project Z - Jira so only those related issues will be seen in these channels and specific teams can subscribe to the channels they care about and will not be inundated with details of other projects they don't need to worry about. 

Collaboration Tools
A quick list of collaboration tools with the use will go a long way when on boarding new employees into the environment or adding different teams into the development studio. 
  • Confluence - Project documentation and requirements are stored here.  Different spaces are created for each project. 
  • Jira -  Issues/Work items are created here.  Each 'project' has it's own project in Jira.  Boards are created to show one or multiple project statuses.
  • Bitbucket - Code repository.  All code is stored in this repo and any changes to code are made through a branch and pull request defined in the development process. 
  • Jenkins/Bamboo/Team City - CI server is used to create builds, run tests (unit/e2e/etc), and do deployments 
  • Webex - Used for meetings with more than 2 people and screen sharing.

Once everyone understands when/where/how to communicate it will save the team a ton of time. 
​
0 Comments

    Author

    Security Researcher with about 20 years in the Computer Security Field. Going to talk even if no one is listening..

    email: mrbartlett <at> mrbartlett.com

    View my profile on LinkedIn
    Picture

    Archives

    January 2022
    June 2021
    February 2020
    June 2019
    October 2018
    September 2018
    August 2018
    March 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    December 2015
    August 2013
    January 2013
    September 2012
    June 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011

    Categories

    All
    Activation
    Agile
    Backup
    Centos Vmware Interfaces Error
    Collaboration
    Communication
    Computer Security Scans Passwords
    Conferences
    Drones
    Emergency Response
    Exploit Kits
    Exploits
    Life
    Links
    Malware Security Dnschanger
    Organization
    Passwords
    Patches
    Phish Security Email
    Project Management
    Rfun
    Scrum
    Security
    Security Blackhole Exploit Kit Browser Phish
    Security New
    Software Development
    Team
    Windows
    Work

    RSS Feed

Powered by Create your own unique website with customizable templates.