While developers focus on code, architecture, performance and engineering, the Program Manager focuses on the big picture "what are we trying to do", what does the user want, how would the user experience be and how would the product be used. This involves liaising with the developers and working through the entire SDLC as an advocate for the end users and the customers.
From envision of the project till its delivery, a Program Manager sports multiple hats.
Learn Phase
- Understand customer problems, learn about products and technologies that are relevant to these problems
- Come up with a conceptual model to capture the way customers would like the feature set to work
Output of this phase
- Prototype (of varying fidelity) - it could be a drawing, high fidelity diagram, static screenshots etc.
Convince Phase - This is when the fun begins !
- Convince peers, manager and the development team that the ideas are worth pursuing.
Output of this phase
- Project Plan and Goals
Spec Phase
- Summarize entire set of features, functional design, systemic interactions, boundary conditions, localization, user interactions, security etc. in the form of a document that's consumable by developers, testers, usability and product designers
Output of this phase
- Refined Functional Specifications
Refine Phase
- Refine the functional spec with details based on developer and tester inputs during the development phase of the product
- Test the final product once ready to ensure the design expectations are being met and collect initial user feedback on the product
Output of this phase
- Final Product
No comments:
Post a Comment