I have to agree. First implementation of agile/scrum I worked with was a bunch of printed cards nailed to a board where in the daily meetings the PM used a pen

I have to agree. First implementation of agile/scrum I worked with was a bunch of printed cards nailed to a board where in the daily meetings the PM used a pen to take hours out of it, or add more if we decided it was going to take more. After the meeting he took the cards to his computer and wrote some kind of report (no idea the format). Second company about the same except PM didn't do the report after but still post its on the wall. And it all worked great, then I got to the third company and no board, just tickets in Team Foundation the programmers had to update every day (heck, they even asked us to update various times a day). We had a daily meeting but not much else. Truth be told, I usually just forget about the hours update, whenever I closed a ticket I just looked at the estimated time that was there (which wasn't decided by me) and put that as working hours. I was bugged everyday to keep my hours up to date because it was very important some higher up had a general idea on how things were going... Here is the thing, first two places started using agile/scrum by reading online and books, third one payed a consultant more than 25K to implement this system.