High-Tech Yuga

Even-though scrum master and product owner work closely together their roles and responsibility are different. Mostly product owner from buying organization and scrum master from selling organization. A scrum master leads the development team  and seeks input from product owner to get user stories  prioritised  and update status to product owner. As you aware product backlog is crucial for the agile project development. It contains all the user stories needs to be delivered during the project. Product owner need to ensure the product backlog is available to the scrum master and it contains the needs of customer, business, sales, marketing team and all other relevant stakeholders. Once the product owner create the vision for the project, it’s scrum master’s responsibility to bring the vision to live. Scrum masters are responsible for adopting and implementing agile methods to increase team productivity, efficiency, and improve the quality of the deliverables they have been tasked to cre

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: Epic) Sprint Plan (S

Monitoring and Controlling is the largest and continuous part of the project management. It keeps eye on everything that’s happing in/out of the project and adjusts as needed.   A good project manager is constantly monitoring every single thing happing in the project. If you find the problem latter it’s hard and more expensive to solve it. The below practices need to be followed by a project manager for an effective monitor and control of the project: Project meetings: Conduct the project meeting on daily (daily scrum) or weekly basis without fail and ensure that all the team members joins. If the team is not co-located use the audio conference/video conference. Make the meeting shot, come up with action items and send the Minutes of Meeting (MoM) at the end of the meeting. Need to follow up with team to close the action items on the agreed target closure date. Discuss on the status/issues and provide help required for the team work on the tasks. If possible use the online tools to

Definition of Done (DoD) is a list of requirements that a user story must adhere to for the team to call it complete. While the Acceptance Criteria of a User Story consist of set of Test Scenarios that are to be met to confirm that the software is working as expected. Acceptance criteria:  Acceptance criteria or  Acceptance scenarios are an integral part of a story. The  acceptance tests define what actually has to be built to implement a story. There is no allocated responsibility for writing acceptance criteria. While it is usually the product owner or product manager who gets around to defining the functionality, just about anyone on the team could write acceptance criteria for user stories. The writer must be careful to ensure that the acceptance criteria are written from the perspective of the end user, and for this reason the product owner (who is considered to be the voice of the customer) often undertakes this task.  The acceptance criteria written in this format Given - When -