public notebook from daily architect, developer and trainer experiences
Stakeholders
List: Name, Role, Department, Email, Telephone
Roles: Sponsor, Decision-Maker, SME
Classification
— Salience: power, urgency, legitimacy
— leading, supportive, neutral, resistant, (unaware)
— Power/Interest, Influence/Impact
Procurement / Partner
Roadmap
Time & Scope
Milestones & Deadlines
Continue reading “Project Manager: Onboarding Checklist for Existing Project”See article on LinkedIn https://www.linkedin.com/pulse/deep-dive-product-backlog-invest-stories-create-smart-gaurav-sharma-1c/ from Gaurav Sharma.
The prioritization of backlog items is one of a product owner’s / project manager’s main tasks. However, it can be very difficult to develop an objective methodology. One example – I have used in different variations – is following:
For each dimensions there can be max 5 point. The business value is the (weighted) sum of the dimensions:
I recently read this article (“Managers — Look at Your Engineers’ PRs“) and absolutely agree. In fact, I have done this for a couple of years now and I agree that is a valid and valueable source for feedback – besides the 180 degree feedback from colleagues.
However, I wouldnt just use the PRs for individual performance review but also to track the team performance. PRs reveal a lot of team dynamic (how is the communication between team members) and product/software quality. In a more junior team I would also attend a more active role in PRs to support or fill the role of a senior developer.
A definition of done (DoD) can help your team to maintain the quality of your product. Often it is helpful to have not only a DoD for a feature in total at the end of the sprint, but also for the steps in between. This articles provides you an example from a real-world project as a starting point.
Continue reading “Definition of Done: a real-world example”