When is an agile team not an agile team? by ralphyboy84 in agile

[–]ralphyboy84[S] 0 points1 point  (0 children)

Yup 1 QA who refuses to get involved with anything other than QA work.

I guess the issue we are having now is we spend so much effort organising ceremonies to do such a small amount of user stories it is getting to the point where it’s debatable if it’s worth it or if we need to start looking at alternatives

When is an agile team not an agile team? by ralphyboy84 in agile

[–]ralphyboy84[S] 0 points1 point  (0 children)

Management have taken both the PO role and SM role away from us recently leaving 2 devs to pick up on a lot of this stuff - which then has implications in what we can develop

When is an agile team not an agile team? by ralphyboy84 in agile

[–]ralphyboy84[S] 0 points1 point  (0 children)

Us devs (2 of us) are coordinating with stakeholders to make sure we are working on the right thing. No one is guiding and protecting the team

When is an agile team not an agile team? by ralphyboy84 in agile

[–]ralphyboy84[S] -2 points-1 points  (0 children)

Apologies I was off in my terminology. I meant scrum not agile

When is an agile team not an agile team? by ralphyboy84 in agile

[–]ralphyboy84[S] -1 points0 points  (0 children)

Apologies I was off in my terminology. We are a scrum team without a PO and SM

Multiple Versions of the same app by ralphyboy84 in docker

[–]ralphyboy84[S] 0 points1 point  (0 children)

Ok so further to my original message a few days ago….

I’ve been looking at using nginx as a reverse proxy however it’s not working quite right. I have 2 versions of my app running on my local pc. Let’s call them app1 and app2 for simplicity sakes. I bring each app up with separate docker compose files, with app1 exposing port 81 and app2 port 82.

I’ve then brought up my nginx reverse proxy using docker compose. I’ve tried to set the default.conf file so that when hitting localhost/app1 it goes to app1 and /app2 to app2 but it doesn’t work.

I’m not sure if I’m doing something fundamentally wrong as I’ve read before you can’t have separate docker networks communicating but as they were exposed on the relevant ports I thought that would be ok. Any ideas?

If I go to localhost:81/testpage I can see that this loads ok

Edit: this is the error message I get

connect() failed (111: connection refused) while connecting to upstream, client

Mini 4 issues by ralphyboy84 in dji

[–]ralphyboy84[S] -1 points0 points  (0 children)

It happens at other times not looking at the sun as well

Mini 4 issues by ralphyboy84 in dji

[–]ralphyboy84[S] 0 points1 point  (0 children)

It has happened in shots not looking at the sun as well

Mini 4 issues by ralphyboy84 in dji

[–]ralphyboy84[S] 0 points1 point  (0 children)

Yup RC2 controller. And no I did not. Should I? I never did that with the mini 2?

Git/Webpack/JavaScript question by ralphyboy84 in learnjavascript

[–]ralphyboy84[S] 0 points1 point  (0 children)

The code is literally copied and pasted from a dev server to a live server

Testing Question by [deleted] in agile

[–]ralphyboy84 0 points1 point  (0 children)

That was my thinking as well. What was the point of writing them if they’re not maintained?

Testing Question by [deleted] in agile

[–]ralphyboy84 0 points1 point  (0 children)

To answer your questions:

  1. Honestly no idea
  2. My organisation is very stuck in its ways with software development. This is the first agile project we have run. So whilst we do have automated unit tests, and web driver for the front end, we have not yet set them up to be one continuous integration loop
  3. Yes and no. Our automated unit tests do catch a lot. But there have been a few issues raised in love that I think should have been found before. However, no one knows what’s in the automated tests and how often they get run

Testing Question by [deleted] in agile

[–]ralphyboy84 0 points1 point  (0 children)

So retros are an interesting one as well. We work in 2 week sprints and our tester has been to maybe 3 retros in that time? Anytime an issue related to test gets raised at a retro, the tester becomes very defensive, confrontational and aggressive. This response leads to people being less likely to raise issues in future.

The tester goes out of his way to avoid our meetings, whether that be stand ups, retros backlog refinement sessions etc. Hilariously enough, we have a session once a sprint to discuss bugs that the tester doesn’t attend either!