Suggestion: Info in item information screen

Plc consider to add - information is item tradable, no-refundable /not tradable etc


Still THIS this so far was and is advertized as RCE, so all items would be tradable...
Resnis

Now comic part how thing might go ....

Ps estimates in normal dev
1. PM_0 - Management decision - 5min , adding to schedule/release plan 5 min
2. ANA1 - Analysis 10 min (data already got to be in DB ,.. need to add in view only as new line)
3. RQM1 - Specification ~ 15 min
4. DEV1 - Coding (view - to display) = 30 min
5. TST1 - 10 min testing (thing what MA never does in-house ... )
6. REServe - Wasted time ~ + 1h (things never are 100% straight (//reserve))
7. BLD1 - Add to patch ... 2 min
8. DEP - no seperate VU, = 0 effort additional needed , Deployment in staging environent 1, and PROD 2nd
9. MNG - Management overhead 15 min
so total ~ 2 h - 2.5h
time till deployment ~ 3 workdays needed (duration)

MA approach -
1. PM_0 - Postpone Analysis 3 years - Effort in analysis 0 in junk communication ~ 50h
2. ANA1 Forget to do analysis when time comes actual effort = 0 but written off ~ 50 h ?
3. RQM1 - - just not done - WHO needs 2 specify ... in Ninja coding
4. DEV1 - Add new code (crating new 5+functions, 7+ DB calls etc .. Game size +150MB as lots of junk added as well )what calculates values what are written in code as text (plan text .. why any1 needs optimization), (not re-use existing,... ), not using any technical coding standards, Coding done by 1 year drop-out student , what was not even capable of study of economics...
5. TST1 - 0 testing (thing what MA never does in-house ... )
6. REServe - Who need reserves in ninja coding ?
7. BLD1 - Add to patch ... adding in 3 patches , as no documented then messed up builds 4 times each, + 2 times Bug fixes
8. DEP - no seperate VU, = 0 effort additional needed , 5 h as need 2 separate bugfixes at least,...

9. MNG - Management overhead 50h

10. - bug analysis - 5 h
11. roll back - 20h 2 times as all things failed
12. Bug fix dev - 5h need 2 times at least
13. Mess all things up ... Analysis_3 ... 15h

14. Aditional Management overhead for Crisis management- 100 h +

15. Never gets implemented
16. In surprize case ... if get implemented ~ 3 year duration ...

Total ~ 200h needed 2 add 1 line in a form ... to display data what are in DB already ...

sadly you are very right here.

the impression fortifies that MA has pulled the plug on further development, innovation and bugfixing of their (one and only working!) product.

but this is an understandable management decision:
else MA would risk to gain new / to lose less / to please their customers, which would mean more work for MA. and workload must be minimized!


MA:
scrap the catastrophic side show projects!
concentrate on the game!
because: i only pay for the game!