This thing targets people who started using Photoshop back in the day when it still wasn't a subscription service for basic and mildly advanced image editing tasks, and who thus grew accustomed to the Photoshop UI. Shortening the chain will mean less integrated decision making and will increase the amount of surprise and inconsistency in the product and its delivery. The processes are designed for predictable, consistent delivery and to minimize surprise. Can work if you roll out gradually and are very responsive to any reports of regressions.Īll in all, this is unlikely to happen in less than a couple of weeks. Some people fly by the seat of their pants, and rely on fixing things in production if it breaks in production. There will be some measure of QA, ideally. You'd only change the sprint scope if the team is running out of work to do or there's a major customer request or other panic.
Then it'll go into a sprint most probably, but not the current sprint, because that would change the scope and affect estimates and possible delivery timelines.
There may be some communication between product and design to figure out how it should look and feel. Usually, feature requests go through a product manager who can do analysis, integrate with road map, prioritize against other features, figure out if there's overlap with another feature (maybe one coming up soon) and so it shouldn't actually be implemented, etc.
0 kommentar(er)
