The Story So FarRead Now
In project management, what has historically happened is that 1 person manages requirements (Product Manager) and then each person who works on keeping the product functioning has a boss who maybe manages them to their professional detriment, and possibly the diminishment of the product. The project manager then vacillates between saying how soon it will get done, and which manager's silo is the cause of delay.
Because products are still getting developed until they are sunset, in Scrum there's no "post-development maintenance period" which I am aware of. So, exclusively "managing but not developing" any product, in the working paradigm of Scrum, isn't actually a scenario, is it?
Leave a Reply.