just have to get a project team together and hash out

Posted on: March 20, 2020 at 10:18:28 CT

the requirements so they can submit it to the IT department. After they respond with their estimate of hours, it can go up the ladder for approval in next Thursday's board meeting. Once approved, the sign-off will go back down the chain and assigned back to IT. IT will take it up in their weekly backlog meeting and prioritize it for the next release. 2 weeks later, the development team will pull it into their workflow and some Indian guy can edit the html and change "April" to "July". Then it can go to QA where people will pretend to test it and finally to User Acceptance Testing. Once all of the additional asks are pushed in and scope creep reaches maximum inefficiency, it will be packaged in a release and sent to change control.

you get the picture