Scrum for web agencies, does it really works?

On last T3CON19 I was having a speech about how Scrum works in web agencies.

My slides are visible on slideshare https://www.slideshare.net/davdenic/

Enjoy :-)

Install ckeditor 4 version basic via npm



Instead of installing the full version and disabling plugins in the configuration you can get the basic version via npm using the ckeditor-releases repository.

run in terminal:
npm i ckeditor/ckeditor-releases#full/latest --save


or just add to your package.json:

"dependencies": { 
    ... 
    "ckeditor": "github:ckeditor/ckeditor-releases#basic/latest", 
    ... 
 }

Serveo is a ngrok like free alternative to expose your localhost

Serveo is an alternative to ngrok.

PRO: does not need to download a software or to register to a service

CONS: no fancy dashboard

usage

ssh -R 80:127.0.0.1:32775 serveo.net

it generates a subdomain like https://volens.serveo.net/  that redirect the traffic on your local machine on local port 32775: http://127.0.0.1:32775/

I'm using it on DDEV and works also with the XCode Simulator.

check it out at https://serveo.net/#manual


Git delete merged branches


LOCALLY


git branch --merged | egrep -v "(master|development)" | xargs -n 1 git branch -d


Dry run

git branch --merged | egrep -v "(master|development)" | xargs -n 1 echo



REMOTELY

git branch -r --merged | egrep -v "(master|development)"| grep origin | sed 's/origin\///' | xargs -n 1 git push --delete origin


Dry run

git branch -r --merged | egrep -v "(master|development)"| grep origin | sed 's/origin\///' | xargs -n 1 echo



Once you delete the branch from the remote, you can prune to get rid of remote tracking branches with:

git remote prune origin

CSS hover apply to parent elements


Imagine you want apply the hover effect to the whole parent element but just when mouse over a child element, pure CSS no JS

Here the trick:


Mac Xdebug PHPStorm DDEV Docker when the normal configuration fails

Setting up Xdebug on PHPStorm seems pretty straightforward, easy and quick, just following the brainless Zero-Configuration Debugging right?

Well not in my case. Or better, it was working fine but suddenly it stopped working. And after resetting everything and digging hours on stackoverflow and blogs, at the end I came to this solution, basicly forcing docker and my Mac tunnelling

Here my solution




If you want read the full article when I come to the working solution, click here:
http://jamescowie.me//blog/2016/12/all-hail-xdebug-and-lets-let-var-dump-die/

TYPO3 on Mac easy with DDEV and Docker

Do you like have a TYPO3 dev environment or just testing the new version 9 on MacOS?
Follow those simple steps with ddev:

What's wrong with the daily? Why teams want skip it?

I've heard something alarming from a couple of teams i had the honor to serve in past and current days.

They want skip daily the day after planning!

For me it's an absolute no-go, but why that's happening in different teams is the question? Is it just a coincidence?

So I asked the same question to other Scrum Masters and in a well known group of scrum experts and I got different interpretations.

Some scrum masters told me "why not skip it if the team like it?" or "if is the day after the planning they don't have much to sync".
And asking team members I got answers like that: "since we had the planning yesterday we don't have nothing to report" and defend the position with "we agreed that with the former SM, why you bother us with that question again?".

I got the idea those guys think at the daily just like a report.

What I learned as SM and former developer is exactly what's written in the guide, the daily serves to plan the today's work:

The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

For me that's simple, the daily is a must and should be done in each day during the sprint.
Of course not when one of the other main events like review or planning occurs in the morning (or at the daily time in general).

But again why this doesn't happen right now?

I think, it's because the "3 question approach" is interpreted like a sort of report, and often in direction of the PO instead of the team.

How can we have a more useful daily? I think a solution is to find another "structured" way to help the team mates. In fact the current is a very simple template to follow. Can we build another simple template but more collaborative one?