You don't actually know if something works until it's fully integrated and functioning under real load, used by real customers.

Big bang releases? Just say no
13/13

There is no up-front plan, though there is an objective (solve the problem). There are no fixed acceptance criteria. There are no tickets. There is no schedule (though you work as small as possible, so "within a couple of days" will do).
6/7

2) Just before the work starts, have a conversation where you collect enough detail to _start_ (not finish) the work.
3) Start.
4) As you're working, get feedback ("Hey Fred, come over and take a look at this!"). If necessary, adjust what you're building based on that feedback.
4/7

A "user story" (the unit of work) describes a user's problem, not a solution. Anything we build that moves us toward a solution to that problem is fine.

There is no up-front plan. There is no predetermined acceptance criteria. There is no schedule. Don't see how that's a "tiny waterfall."

great :)

also, you could ssh to the iDRAC port and use racadm provided to you there.

racadm set System.ServerOS.HostName <new name>

from the top of my head. can check tomorrow

well, I use iDRAC web UI. sometimes racadm

That's a moving target, so discover what that is through feedback from small incremental releases.

There is _always_ more work than budget (or time), no matter how you work. Solve that by continuously assessing what to do through the lens of user/customer (and therefore, business) value.
4/5

Now assign the team to the product (not projects) that provides the most customer and business value. This is a basic Lean concept: bring resources and people to the constraint—the place with the most demand.
3/5