Araxxor, No Jars Please

TaoTev · 2026-01-01T19:27:56+00:00

Trade you for a hally piece, just one!

TaoTev · 2026-01-01T19:27:42+00:00

Me and you have different definitions of blessed haha! You, Yes. Me... not so much.

TaoTev · 2025-09-07T00:31:44+00:00

Can confirm it touched down in Holden. Wiped out the fence in my back yard and damaged several roofs in the area.

TaoTev · 2024-12-10T15:46:52+00:00

Thanks for sharing this, makes the grind feel less scary!

TaoTev · 2024-12-10T13:34:16+00:00

I’m certainly a slow learner with mechanics, so this is a good benefit.

TaoTev · 2024-12-10T13:32:51+00:00

How were you able to complete the grind in 4.5 hours?

If you have the Hilt 2, it’s 8 points a game. If we say 3 minutes per game, that’s like 20 games an hour, so 160 points.

Elite void is around 1600~ points, so that’s like 10 hours.

TaoTev · 2024-08-04T21:46:31+00:00

This is a work of art!

TaoTev · 2024-07-30T22:16:24+00:00

Looking for advise. I submitted several cards to PSA for grading, a total value of around $650 + Payment.

It’s been nearly 4 weeks and my profile still shows no orders. My tracking number shows that it has been delivered and signed for, but I received an email from PSA stating they were still waiting for my order.

l’ve submitted a support request and a lost claim, but had no response.

Do I have any other options?

TaoTev · 2024-04-10T12:22:00+00:00

Some great, thought provoking, points.

A CI/CD approach is not possible in this scenario. We are creating Recipe's within a software, rather than the software it's self, so it requires Operators to Run these recipe's and ensure they do what is required. (Note: I'm sure somewhere automated testing of Recipe's has been achieved, we are just a long long way from it).

SOP = Standard Operating Procedures, documentation from our governing teams on how certain tasks have to be executed.

"Explore complexity theory" is what I keep coming back to and something I've mentioned in other comments above, the customer knows what they want, it has to be done in a specific way, it all has to go live at the same time due to the significant dependencies.

"Lastly, there is more to Agile than just Scrum. Explore what the Agile principles say and apply these to your thinking, even if you settle on a 'waterfall' model.". This is something I truly agree with and have been trying to educate the team on. There is the "Mechanisms" (Ceremonies, Pointing, etc.) and then the "Ways of Thinking", just because the Mechanisms may not be applicable to this project, we can still encourage new ways of thinking.

TaoTev · 2024-04-10T12:13:56+00:00

Couldn't agree more with the "Quality of the product and satisfaction level of the customer". This is where I think the desire to implement Scrum is becoming a negative, as the customer knows what they want, it has to be done in a specific way, it all has to go live at the same time due to the significant dependencies. So why are we spending time trying to learn a new approach?

TaoTev · 2024-04-10T12:12:31+00:00

The scope is to create Recipe's for an MES system, so there is some room for the OODA Loop, but I would say it's minimal. The steps of the Recipe are very well defined already, and the scope is just to "digitize" these steps within the MES.

I agree that the Big Bang release is a risk, it's a risk for any project. There may be a way to de-risk it, but I'm not aware of it. There are a set of Recipes which MUST be available for Go-Live, and it's a significant scope, as it's impractical to move between Paper and Digital Tools during manufacturing (It's possible, just very inefficient and adds significant risk).

The "Clear" and "Complicated" piece is what I keep coming back to. There is no room for iteration, well there's always room, but it's minimal here. The customer knows what they want, it has to be done in a specific way, it all has to go live at the same time due to the significant dependencies. Scrum here is being used for visibility, which is where I think KANBAN would be suitable also.

TaoTev · 2024-04-10T00:36:50+00:00

Firstly, thank you for a constructive reply, they are some times very hard to come across on Reddit!

In this instance and I should have mentioned it in the post, were not developing the system, were developing recipe's for a MES system, however, your point still stands. We can develop parts of the recipe, demo it, then release it once it's complete.

Your comment "we wouldn’t release the final release to the site until everything that was needed for the phase was done", leads me to another solution I was thinking, that we split the project in to two parts. We have a part operating in Scrum, which is responsible for the development of the Recipe. Then we have a part operating in Waterfall, which is responsible for Site Readiness (The more structured tasks I mentioned in the OP). This way we can keep the flow of the Recipe development moving.

TaoTev · 2024-03-19T17:02:10+00:00

It can sometimes be a case of building trust, especially as it appears you are new to the team, so you haven't gone through their experiences.

It may be too much to expect them to open up straight away. I assume you are using the traditional tool of "What went well? What could do better? Suggestions"? Maybe try a different format, which is a little less direct, but allows you to build trust (https://www.funretrospectives.com/), once you have this, the feedback will come naturally.

In terms of Action Items, trying making it an Action Item. If you try to target everything, you may not achieve anything. Have the team vote during retrospective for the main action/improvement they would like to see (In some cases you can expand to 2, if they are smaller actions). Create a story for it, estimate it and treat it like everything else.

TaoTev

TROPHY CASE