Skip to content

iminavo/scrum

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 

Repository files navigation

📅📊 Scrum 🔮🎲

Context

I started as a /strong/ mid, currently a senior Scala developer in Gdansk, Poland, but my employer - YAPS /jæps/, has offices all over the world for about 6000 strong staff. I'm in a team of six, and together with a similar team two similar teams, we are building a ticketing system, to replace a third party. We work remotely - people from different time zones and domains. We need management, and we have it.

Here I will /try to/ keep my notes on processes at my company, in the form of discussions.

Charachters

Current

Phillip Chen - Our leading architect. He is from Trois-Rivières, Quebec, Canada.

Zoey McBragh - A high-ranking YAPS project manager.

Aleena de Goors - An automation test engineer.

Petr Zapletal - My new team lead

Oleg Kuznetsov - A /witty/ junior scala dev

Sofia Huppmann - A mid-scala dev

Alexander J. Liu - A senior dev

Anton Chernenko - A senior dev

Argen Alimbekov - The team lead of the second team

Dave Gurnell - Architect

Ganesh Kumar - My team's project manager

Ciara O'Flynn - Our busyness analyst

Amina Farzi - The QA automation lead

Jose Manuel Fernandez - Our delivery coach

Andre Sorbasz - A manual test engineer

Sandro - guest, a friend of mine

No longer on the project

Vitar Robasz - Our PM, a former Java programmer of seven years.

Daniil /Dan/ Kmetiuk - Our team lead.

Mark Sachsenheim - The lead of team 2.

Karina Skorodyadko - A business analyst.

Sai Prabhu - A senior Scala developer.

Raimbek Saparov - A mid-scala developer.

Note semantics

I've noticed, that some of my notes may be too emotional, and I'd like to keep personal likings and banter out of these notes. When I return to them later, I weed out the unimportant bits. It may be so, that after this, the outcome can still be misinterpreted /by me/ later. That is why I decided to do the following: when I need to note facts, I'll use quotes. When you read those, please don't just look at my intention in the wording. Even when it can be interpreted as an intention, that is due to my bad writing. I'll do my best to avoid such cases. When I need to express my thoughts, I'll use the normal text.

Below is an example:

| Narek wasn't able to complete his tasks for the fourth sprint in a row

The issue seems like it could be remedied by a helping hand. Unfortunately, we do not have tools in our processes, 
that express pair programming.

The quote does not express my frustration but states a fact about Nareks' progress. I express my feelings with the normal text below, where I find a certain fact about our workflow rather daunting.

About

Stories of scrums, that happen to me

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors