The PC3 process was one example of a "commercial" fork of C4. You can make others. Let me try to answer your questions:
> 1. What is the role of a Product Manager / Product Owner in the process? They'd be the ones testing or organizing testing, ensuring issues were reported cleanly, and ensuring developers had resources to work. > 2. Who can approve that an issue is valid to be developed? Every issue should be fixed or rejected. If there's dispute about direction, this is up to the product owners. > 3. Where in the process does the Graphic designer / mockup of UI go? On-demand help when needed, certainly not upfront UX/UI design. (They usually hate this.) UI design should be like code, solutions to well-defined small issues. > 4. It seems a lot of power is taken from the Product Manager, any suggestion > how to convince him? (no roadmap, no features...) He still owns the overall process. However it can be very hard for people used to an existing waterfall process to get incremental growth. Perhaps show them the blog article on Simplicity Oriented Design. Perhaps one worked example over a few days. It can be difficult, this is why organizations pay expensive consultants to walk them through such shifts. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
