This is a list of some good agile practices. It is up to you to utilize this list and to choose which is the most suitable and useful for your team, project or organization. Experiment and enjoy.
Scrum and agile practices are important. They are good for establishing healthy habits and discipline needed for project success. I am sure that you’ll find them useful, but is there something more there?
This is a list of preparation tasks which might be useful for Scrum fresh start.
9 Employee Engagement Archetypes Re-published from HBR.org
This is ThoughtWorks Maturity Model for the software development and can be easily translated to the agile environment.
This is an example of a good and real Definition of Done list, I helped the team to create.
Here are pros and cons for #Estimates vs #NoEstimates. I don’t judge. I believe that there is no general rule for using these, but you need to listen and to help client/team/managers to make the decision which is the most useful for the product/project.
Why estimation is important? Estimating prioritized backlog, we are making transparent to business side what (roughly) can be done in the following period. Estimations in time are dependent on may factors: experience of the developer, we need to know who will exactly work on this if we want to estimate – and this is usually not known in advance etc.
Based on Dan Pink’s articles and books, money can be a motivator for jobs without great uncertainty and mostly in mechanical jobs, with very small degree of expected innovation and creativity. When non-linear productivity is present, with great degree of uncertainty and where innovation and creativity do finishing the job, there are three main motivators:
As a Product Owner your main duty is to keep Product Backlog in a great shape, in condition which is enabling developers to work on PBL items. So, this is what you need to take care about:
- Page 1 of 2
Showing 1–10 of 13 results