Image for post
Image for post
Photo by Clément H on Unsplash

If you want to test a a NodeJS application with Jest, you often need to set local environment variables. Usually these variables are set on the server when deploying your application, but they’re not available locally for testing.

A common pattern is to use a .env file with all variables for local development and testing. However, to load these variables before you run your test can be tricky.

The magic line is:


Image for post
Image for post
via Giphy

The responsibilities of the Product Owner in Scrum are frequently misunderstood and misinterpreted. As a result, thousands of “Product Owners” around the world do harm the team performance more than they help. Here are a few symptoms which tell you, whether you’re off the track as a Product Owner.

You manage people instead of the product


This is a growing collection of my learnings from building web applications with AWS Amplify

Image for post
Image for post

AWS Amplify is a wonderful idea. In theory it simplifies all the messy coordination of different Amazon Web Services and speeds up building new products. In practice however, Amplify is not quite there yet. Here I describe my learnings of how to use Amplify in practice and how to circumvent the inevitable problems with a new technology.

The paragraphs are in no particular order — I will add to this article each time I discover a solution to a non-obvious Amplify challenge. Feel free to come back frequently and learn from my journey. …


Or: Would you trust a Geiger counter to save your life?

Image for post
Image for post
Photo by Ra Dragon on Unsplash

Disclaimer: I love Scrum — it’s an awesome framework! But too many people believe that Scrum would make their company agile; this is wrong and this is why I wrote this article. Enjoy.

When I went to Chernobyl, a good friend told me to bring a Geiger counter (a device that detects radioactivity) to protect myself. So I got a Geiger counter — a good and expensive one — and went into the danger zone polluted by the nuclear catastrophe of 1986. Although the situation felt scary, I had no fear, because I was protected by that Geiger counter. The device was clicking along happily. Trusting it to save my life, I entered the ruins of the old power plant. I was using the Geiger counter exactly as I was instructed. …


In today’s climate, it’s best to assume that most business models, even successful ones, will have a short lifespan.
― Alexander Osterwalder, Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers

Image for post
Image for post
Photo by Skye Studios on Unsplash

If business models have a short lifespan, how can we create long-term success for our business? Do short lifespans for business models automatically mean short lifespans for companies?

Your business model must change constantly

The solution to keep your company in business in todays quickly changing world? Constantly change yourself! Adapt your business model. It needs to adapt to changing markets, trends and technologies. And this is not a one-time stunt: you need to set up your business to be able to change constantly and quickly. …


A hands-on process we use to get from feature requests to happy customers

Image for post
Image for post
Photo by Clem Onojeghuo on Unsplash

Doing lean startup and customer development in practice is a challenge. Here is how we at gixtra.com get from features requests of users to happy customers.

The full process

Here is the process in short. I will describe it in more detail below.

  1. Receive requests via Intercom
  2. Create a user story in GitHub and link it to Intercom conversation
  3. Prioritize backlog on GitHub
  4. Implement
  5. See conversation pop back up in Intercom after closing GitHub issue => inform customer
  6. Evaluate metrics of new feature and ask customer how they use it/like
    it
  7. Remove feature, if it doesn’t bring enough value for core customers

1. Receive requests via Intercom

It often starts with customers asking how to get something done in Gixtra on our Intercom support chat. Instead of simply answering and closing the ticket, we first ask, what they try to achieve. This often gets us to a whole new level of understanding the context and problem they face on the job to be done! …


Image for post
Image for post
Photo by Tirza van Dijk on Unsplash

This is a beta article. I write and extend this article as I develop an application in VueJS with Quasar and AWS Amplify (including Cognito). I hope, my learnings will already help some of you even without being a fully written article.

Tools used

  • VueJS — JavaScript framework
  • Quasar — Full frontend stack for web, mobile and desktop apps (based on VueJS)
  • AWS Amplify — Cloud infrastructure and services for hosting, CI, authentication … (a little like Google Firebase and Google Cloud)
  • AWS Cognito — User authentication

Why these tools?

You could argue about this for a lifetime. I simply arrived at these tools after trying out a lot of JS frameworks, UI libraries and infrastructure services. …


Image for post
Image for post
Photo by Tina Rataj-Berard on Unsplash

If you develop a VueJS application, you might have come across the following problem: your CSS styles are working totally fine in development; but after building your project, some styles are wrong or missing.

This happened to me a few times and I want to save you from the trouble in this article.

A naive approach

Sometimes you need to customize the CSS class attached to an element. In my example I had events that had a different status (e.g. “confirmed” and “cancelled”). Each status has a different styling.

So naively I went my way and typed:

Note how I use string interpolation on the <div> element to dynamically change the CSS class depending on the eventStatus.


Never ever let it be 16 minutes!

Image for post
Image for post
There is a reason why the Daily Scrum is timeboxed to 15min max!

The Daily Scrum is a core element of good project management. But I’ve seen too many teams misunderstanding this meeting and implementing it badly. Pointing out common misunderstandings & pitfalls, I want to give you hands-on advice to fix the Daily Scrum and reap all the benefits from this important meeting.

While the first article looked at the pitfall of the Daily Scrum degenerating into a status meeting, this article specifically talks about a lack of timeboxing and the Daily Scrum lasting longer than 15 minutes. …


The Daily Scrum is NOT a daily status meeting!

The Daily Scrum is a core element of good product and project management. But I’ve seen too many teams misunderstanding this meeting and implementing it badly. Pointing out common misunderstandings & pitfalls, I want to give you hands-on advice to fix the Daily Scrum and reap all the benefits from this important meeting.

This article specifically talks about the pitfall of the Daily Scrum degenerating into a “daily status meeting”. Although this is a pretty common pitfall, it is by far not the only one — I talk about another one in part 2 of this article.

Image for post
Image for post
Never let the Daily Scrum become a status meeting! (image: “Great Job Soldiers” by 316th ESC)

The status quo

In my many years as an agile coach I have seen the following kind of bad “Daily Scrums” far too…

About

Matthias Orgler

Agile Coach, Business Innovator, Software Engineer, Musician

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store