Slack
This is our communication tool, and where we have internal meetings, internal messages etc. This program is used by everyone in the office.
How we use Slack
Daily status update
In the General channel give a daily status update when you arrive at the office in the morning.
This gives everyone an overview of what you and your co-workers are working on today, who will be at the office when, and if there are meetings or other events happening.
Slack status
Working from home: Use the "Working Remotely 🏡" status if you're working from home so your co-workers know where you are if they want to reach you.
In a meeting: Set your status as "In a meeting" when going into a meeting, so everyone knows why you're not answering.
Out sick: If you're sick, you can use the "Out sick 🤒" status.
Commuting: You can set a "Commuting 🚌" status if you're coming or going to a meeting, or in transit while working from home.
Channels for the whole team
#general: Our main channel. Here, we announce the first status of the day and other news that we find relevant for all employees of Berú.
#webteam-daily-scrum: Our daily SCRUM channel for the web team. We do a very loose version of SCRUM where everyone, shortly, announces what they'll be doing for the day. We discuss if anyone is stuck and needs help, before going on with our day.
#inspiration: Just like the title says, pure inspiration! ✨ Feel free to post inspirational articles, web sites, graphic design, films etc.
#dev_team: Have a question for the dev's? Wanna announce something as a dev for the rest of the web team? Did something urgent happen? Is a site suddenly down? This is the place to be. This is mainly for the web team.
Channels for the danish team
#indkøbslisten: Please write here if we're out of stuff in the office: soda, office supplies, snacks milk for the coffee etc.
#den-danske-kanal: If you need to coordinate something that's not relevant for our team in Poland, you can do it here.
You're welcome to create more channels for inspiration or a project you're working on.
Wrike
Is our project management tool. Here you will get your tasks, different task dashboards and communicate with team members in relation to solving tasks.
How we use Wrike
Project creation
- The client's project manager creates folders and projects in Wrike under Current projects (include to the client folder as well).
Folder: Use folders for new clients
Project: Projects
A project might be turned into a folder after it's completed. Ex a website is a project while being created, turns into a folder in Wrike when it's launched.
- Add timeschedule to the folder/project-node
Add link to the approved offer (Saved in Harvest, Dropbox etc.) - Add start and end date to projects.
-
Add the label 'Current projects' and add the project to the customer folder.
Tasks
Creation of tasks
- If the task is part of a project: Create the task in the project node
If it's a support task: include task into folder "support" and client folder -
Task description:
Give the task a descriptive title.Add as much information necessary for the person solving the task. Better to add to much than too little.
Consider the following for your task description (technical errors):
Have you tested the error? Add a description of your test, screenshots and link to testpage if you have it.
Add a link and screenshot to an example of the error on the client's solutions.
Add relevant files
Add links to similar errors (wrike tasks) for same or other clients
Is there anything the person solving the task should be aware of? Something unique about the client, about the solution, about the error?
Is there anything that should be done when the error has been fixed or the task has been solved?
Ex: the client wants to see an example of the solution before it's deployed.
Ex: the task should be time estimated and approved before any changes are ma -
Add a due date to the task.
If there is a specific time interval you want the task to be worked on, add this as start and end date.
-
Consider status of the task:
-
Planned (default) - a task is planned when it has a due date
-
Doing - Task will soon begin/has begun ()
-
Late - Will not be done as planned/I'm not able to solve the task (This status notifies the project manager of challenges in the task)
-
Waiting - waiting for client, waiting for deploy or waiting for something else (remember to set a date for follow up and assign the person who should do it)
-
Ready - (eg. for test/deploy/client approval) - remember to assign task to the one responsible for next step
-
Done - Task is closed
-
Backlog - Tasks with no due date (support tasks is added to Support folder), ideas, “We should look into that at some point”)
Ask the project manager if you're in doubt about which status to use.
-
Working with tasks
Use the dashboard "My tasks" in Wrike to see all your tasks showed with a collumn for each status.
Assigning tasks
Project manager will often do the initial assignment of tasks.
Assign tasks to the person who's responsible for the next step in solving the task. If a tasks for instance is ready for testing, then assign the task to the person who's responsible for doing the testing.
Prioritizing weekly tasks
Monday is support day, and wednesday is deploy day.
Working with the dashboard
Each member of their team has their own dashboard, that show the status current and upcoming tasks.
The dashboard is divided into the steps a task goes through before it is completed.
See the description here of how to move your task through the dashboard:
Planned
Tasks that are planned be to solved this week / as soon as possible, are give the label planned.
Be aware of high priority tasks + tasks that have upcoming deadlines or exceeded their deadline.
Ask your project manager if you do not know which task to begin with.
Out of tasks in planned? Look in backlog.
Backlog
Upcoming tasks are given the label backlog.
At the pre-monday meeting tasks are moved from backlog to planned if you should work on them this current week.
In progress
Move the task to in progress when you start working on it.
If you stop working on the task move it back to planned.
Move the task to on hold if you are awaiting feedback before you can continue. Ex: The client needs to respond or give more information.
Ready for test
Move the task to ready for test when someone should start testing it.
Add to the task where it can be tested. Please add direct link to a test page and maybe a screenshot.
Assign the task to the person that should be testing it. Please tag the person in a comment as well.
Testing
Move the task to testing when you start testing it.
Add information about needed adjustments or errors you find in your test. Can be added as comment or sub tasks.
Assign the task to the person that should fix errors found in your test, and move the task to back to planned (or backlog).
Ready for production
When adjustments are finished, tested and ready to be deployed move the task to ready for production.
Assign the task to the person who will deploy the task.
Done
When a task has been deployed move it to done.
!Important!: Do not set the task as completed, since it will then disappear from everyones dashboards.
Assign the task to the project manager. The project manager will test if everything works as it should, tell the client about the update and track time in Harvest.
Done + completed
When a task is done, the client has approved the update and time has been tracked in harvest the project manager will change the status of the task to completed.
Documentation
Is the changes from is task something we should document, so in the future we can remember and update clients on this general change? Then add the label Documentation to the task.
VPN
Not specific software, but you should remember to set up your Berú office VPN. Follow the guide below to set it up.
macOS users
- Open Settings > Network
- Click the "+" icon and chose VPN from the dropdown, use "Beru VPN" as the connection name and select L2TP via IPSec as the VPN-type
- Type in the server address: 94.18.223.98
- Type in your account name: "Beru\your first name" (fx: "Beru\Ask")
- Click on "Authentication Settings"
- Type in your Active Directory password
- Type in the Shared Secret key: Beru#g@2
- Click OK
- Connect!
NB: When setting up the VPN on Mac, make sure you configure all of the internet traffic to go through the VPN, or else the connection can be a bit unstable (you can check this box off in the advanced VPN settings).
Windows 10 users
Go to Settings > Network and Internet Settings > Add VPN Connection
- VPN Provider: Windows Built In
- Connection Name: "Beru VPN"
- Server name : 94.18.223.98
- VPN Type: L2TP/Ipsec with Preshared Key
- Go to Windows 10 network connections > "Beru VPN" properties
- Go to Security > Allow these protocols > Microsoft CHAP version 2 (MS-CHAP v2)
- Go to advanced properties and enter the preshared key : Beru#g@2
- Use these credentials:
Username : "Beru\your first name" (without quotation marks)
Password : Your Active Directory Password
Troubleshooting (Windows users)
- Make sure the mschap protocol is approved in the connection options.
- Possibly this has to be done:
- run regedit.exe
- Find the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent
- Create a new DWORD (32-bit) key: AssumeUDPEncapsulationContextOnSendRule with the value 2
- Restart your PC
If this doesn't help, watch this YouTube video.
Creating a new user
The server is located at the Berú office, so users need to be created from here on that server.
1password
This is a vault with all of our passwords for customer solutions, VPN logins, and tools that we use. Please save all of your Berú logins here, but no personal logins (unless you have your own vault).
Please ask Rasmus for a login for 1Password, and install it on your computer. It's a good idea to install the Chrome plugin as well, especially if you are logging in/out of a lot of customer solutions.
Gas Mask
Gas Mask is a way to access some of our closed development sites. Wether you are a project manager taking a look at a QA site, a film team member looking at a QA site making a background video or a developer, this is a good idea to install.
You can add/remove IP's in Gas Mask with names of our dev sites. Here is a list with a lot of the dev sites (updated 14.06.22). Just copy and paste the following text in Gas Mask:
### Host Database## localhost is used to configure the loopback interface# when the system is booting. Do not change this entry.##127.0.0.1 localhost255.255.255.255 broadcasthost::1 localhost23.88.5.122 owneror-fl1c0k7195.201.85.212 berupro.dk10.0.1.12 dev.gopro.dk195.201.85.212 berupro.dk185.21.41.86 resumedatabase.beru.dk23.88.5.122 finansraadet.qa185.21.41.86 bsmintra.beru.dk23.88.5.122 gobasic3.qa23.88.5.122 gobasic4.qa23.88.5.122 gobasic5.qa23.88.5.122 gobasic5.test23.88.5.122 sum.beru.dk23.88.5.122 designguides.qa23.88.5.122 ditpka.qa23.88.5.122 datv5.qa23.88.5.122 gobasic4sit.qa23.88.5.125 beru.dk23.88.5.125 admin.beru.dk23.88.5.125 undervisning.beru.dk23.88.5.122 bpsintra.beru.dk23.88.5.122 bpsintra.qa# GEUS23.88.5.122 eng.geus.qa23.88.5.122 geus.qa23.88.5.122 geus-campaigns.qa23.88.5.122 vandmodel.qa23.88.5.122 geologiskslutdepot.qa23.88.5.122 mapfield.qa23.88.5.122 mapfieldv5.qa23.88.5.122 geusv5.qa23.88.5.122 geusv5.test138.201.83.113 mapfield.gobasic.org#Coronasmitte dev23.88.5.125 admin.coronasmitte.beru.dk23.88.5.123 coronasmitte.beru.dk#NCE23.88.5.125 admin.nce.beru.dk23.88.5.125 nce.beru.dk23.88.5.125 gribskovsorterer.beru.dk#BSM23.88.5.122 bsm.qa23.88.5.122 vhi.qa23.88.5.122 english.sm.qa23.88.5.122 boernebortfoerelse.qa23.88.5.122 english.boernebortfoerelse.qa23.88.5.122 dkr.qa23.88.5.122 forvildmeddig.qa23.88.5.122 designguide.bsm.qa23.88.5.122 dat.qa23.88.5.122 adipa.qa23.88.5.122 gobasic4sit.qa23.88.5.122 pka.qa23.88.5.122 oim.qa23.88.5.122 nationaltgenomcenter.qa138.201.83.113 gobasicv3.beru.dk23.88.5.122 gobasicsites.qa23.88.5.122 qa.nst.dk23.88.5.122 kefm.qa23.88.5.122 en.kefm.qa23.88.5.122 stk.qa23.88.5.122 ipcd.qa# OIM23.88.5.122 oimintra.db23.88.5.122 oimintra.qa185.21.41.175 oimintra23.88.5.122 cprv5.qa23.88.5.122 valg.oim.qa23.88.5.122 elections.sim.qa23.88.5.122 elections.oim.qa23.88.5.122 oimb.qa23.88.5.122 resumedatabase.oim.qa23.88.5.122 budregn.sim.qa23.88.5.122 budregn.oim.qa23.88.5.122 english.sim.qa23.88.5.122 cpr.qa23.88.5.122 sum.qa23.88.5.122 atag.qa23.88.5.122 blankintranetv5.qa23.88.5.122 simv5.qa23.88.5.122 english.simv5.qa23.88.5.122 english.boernebortfoerelsev5.qa#Repos for Mercurial23.88.5.122 repos.beru.dk#SDFE + GST138.201.83.113 sdfe.beru.dk138.201.83.113 gst.beru.dk138.201.83.113 eng.gst.beru.dk138.201.83.113 navigation.beru.dk23.88.5.122 civilstyrelsen.beru.dk138.201.83.113 inspire-danmark.beru.dk138.201.83.113 danmarksadresser.beru.dk138.201.83.113 eng.navigation.beru.dk138.201.83.113 balticsearouting.beru.dk138.201.83.113 landindspektoernaevnet.beru.dk138.201.83.113 eng.sdfe.beru.dk138.201.83.113 grunddata-ejendom-adresse.beru.dk138.201.83.113 msdi.beru.dk138.201.83.113 datatilsynet.beru.dk#Old hetzner138.201.83.113 6ditpka.beru.dk#New hetzner116.202.234.102 sfst.beru.dk116.202.234.102 gribskov.beru.dk116.202.234.102 vesthimmerland.beru.dk116.202.234.102 hjorring.beru.dk116.202.234.102 dkrv5.beru.dk116.202.234.102 gku.beru.dk116.202.234.102 stk.beru.dk116.202.234.102 ngcdesignguide.beru.dk116.202.234.102 en.kefm.beru.dk116.202.234.102 whistleblower.beru.dk#Hoejskolerne upgrade116.202.234.102 hoejskolernev5.beru.dk116.202.234.102 ffdv5.beru.dk116.202.234.102 hojskolebladetv5.beru.dk116.202.234.102 danishfolkhighschoolsv5.beru.dk116.202.234.102 skoleindkobv5.beru.dk116.202.234.102 hojskolehistoriev5.beru.dk116.202.234.102 test.hojskolernev5.beru.dk116.202.234.102 hojskolesangbogenv5.beru.dk116.202.234.102 intra.datatilsynet.dk116.202.234.102 aalborg.beru.dk23.88.5.122 pkaberetningv5.qa#New SIM upgrades116.202.234.102 cprv5.beru.dk116.202.234.102 imv5.beru.dk116.202.234.102 english.imv5.beru.dk116.202.234.102 valgv5.beru.dk116.202.234.102 electionsv5.beru.dk116.202.234.102 imbev5.beru.dk116.202.234.102 resumedatabasev5.beru.dk116.202.234.102 budregnv5.beru.dk116.202.234.102 hjorring2.beru.dk116.202.234.102 hjorring1.beru.dk116.202.234.102 hjorring13.beru.dk116.202.234.102 hjorring11.beru.dk116.202.234.102 smv5.beru.dk116.202.234.102 boernebortfoerelsev5.beru.dk116.202.234.102 english.smv5.beru.dk116.202.234.102 english.boernebortfoerelsev5.beru.dk116.202.234.102 smintra116.202.234.102 smintra/116.202.234.102 imintra116.202.234.102 imintra/116.202.234.102 ngc2021.beru.dk116.202.234.102 ngc2021en.beru.dk
