DEV Community

Arpit Mohan
Arpit Mohan

Posted on • Originally published at

Distributing operational knowledge across a team

TL;DR notes from articles I read today.

Distributing operational knowledge across a team

  • Knowledge management isn’t just a concern for larger companies. Small teams can & should adopt knowledge management practices and tools right from the beginning. It helps in building a scalable team and an effective on-boarding of new members to the team.
  • Start building your knowledge repositories. These are for information needed in the long term by many different team members.
  • To begin with, use simple tools for task management and collaboration and you can always move to a more feature-rich tool if and when you need to. To make sure people actually use a tool, make the tools usable and relevant and offer any necessary training needed for your team to get comfortable with the tool. Define expectations around particular tools for particular tasks, so that work or concerns are not addressed unless logged with that tool.
  • Find a comfortable signal-to-noise ratio of communication: start with more communication and gradually filter out what you realize you don’t need, rather than missing out what you didn’t know you need to know.
  • Remember the importance of face-to-face contact as well, in person or via VoIP, for clarifications, resolving long-standing issues and building morale. For teams across time zones, make these meetings asynchronous or organize several meetings at different times to allow a fair spread for participation.

Full post here, 9 mins read

Things to remember before you say yes to automation testing

  • All tests can’t be and shouldn’t be automated. Know which tests, if automated, will stop finding bugs and keep them out of the automation list.
  • Work on well thought out and well-defined test cases before starting to build test automation.
  • Use the programming language your testers are familiar with to keep the learning curve not too steep.
  • If test automation gives ambiguous results, don’t consider it. There must be a problem with the test script or test plan. Look at solving that problem.
  • Break your test suite into smaller chunks of independent test cases that don’t affect the results of other test cases.

Full post here, 6 mins read

Get these notes directly in your inbox every weekday by signing up for my newsletter, in.snippets().

Top comments (0)