Agile | Scrum engineering and Quality Assurance best practices

Scrum engineering and quality assurance best practices

Never seperate testing and development. According to the Agile principles devolopers and QA specialist must work together on features.

Address all bugs found during a current sprint in the following sprint to maintain commitment consistency and stable work rhythm.

Always integrate continuous integration to execute automated tests for every finalized feature. This will help to identify potential bugs in a early stage and take the appropriate actions to resolve them.

Continuous improvement: Always strive for better results by evaluating the teams track record and learn.

Connect with us and join the conversation

Thank you for reading this article. Please feel free to share your feedback on the practices we suggsted.

With your help we can continue to improve our Best Practices Library and share our knowledge with the world.

Scrum tracking and predicting best practices | AGILE

Scrum tracking and predicting best practices

  1. Use the burndown charts to visualize the progress of the sprint to determine that the sprint progresses according to schedule.
  2. Use the release burndown chart to estimate how many sprints are needed to complete the project on schedule and whether the timeframes must be adjusted.
  3. Use velocity as measurement to visualize how many stories are completed during each sprint compated to initital estimates.
  4. Take time to choose the right collabration software that fits the teams needs.

Agile – Scrum managing the sprint and product backlogs best practices

Scrum managing the sprint and product backlogs best practices

  1. The product backlog and sprint backlog seperate must be managed seperately to ensure you can plan, efficiently estimate ,and forecase your sprints.
  2. Stimulate teammembers and stakeholders to verify all outcomes and results and provide feedback as applicable by making all scrum related documentation available and accessible.
  3. Use task prioritization techniques in the product backlog to identify priorities and key features.
  4. Always use unique IDs to identify each unique user story or items in the backlog. This will make it easy to keep track of tasks and stories no matter how you call them.
  5. Use Excel as tool to create your backlog and prioritize and reprioritize the tasks quickly and easily.
  6. Use a Scrum board to create visibility of each sprint.
  7. Reprioritize your Product Backlog each time you add to it. It will save you trouble in the long-run
  8. A sprint backlog must be centered around one specific goal.
  9. Be as specific as possible with each part of your Sprint and product backlogs stories.

Agile – Scrum planning and estimates best practices

Scrum planning and estimates best practices

  1. Work together with stakeholders to estimate the product backlog to establish transparency and help reduce the change of potential conflicts around estimates.
  2. Ensure sufficient product backlog items are identified and confirmed before you start with the sprint planning. This will help to determine the correct scope of the project.
  3. Translate team and stakeholders objectives into clear sprint goals to ensure they are aligned and transparant.
  4. Use Planning Poker to make better estimates.
  5. Use 6-hours days leaving the remaining two hours each day for risk mitigation or unexpected events.
  6. Never stretch or cut sprint time because using specific timeframes is one of the key elements of the scrum approach.
  7. Reprioritize the work that needs to be done to meet the project goals.
  8. Use discussions during meetings as input for continuous improvement of the scrum project.
  9. The sprint planning meeting should take no longer and no shorter than four hours.

Agile – Scrum teamwork and meetings best practices

Scrum teamwork and meetings best practices

  1. Define clear objectives: Fill the product backlog together with all the involved stakeholders and the scrum team to algin their vision and understanding of the future product or service.
  2. Always begin and end on time with scrum meetings. You need to stick to the agreed schedule no matter who is there to attend the meeting.
  3. Don’t break existing teams to start a new project and use their collobration experiences from previous scrum projects.
  4. Practice stand-up meetings (stand-ups / daily meetings) to get the team comfortable with this approach.
  5. Ask stakeholders and product owners to participate on a regularly basis in the daily scrum meetings to improve communication and understanding.
  6. Create communication guidelines to ensure teammembers are trainend on effective communication skills and understand the importancy of communicatin.
  7. Empower team members to adapt their development approach as changes occur or problems arise.
  8. Use a central hub for User Stories, tasks lists, burndown charts ,notifications, comments and feedback.
  9. Promote peer-to-peer collabration to improve mutual respect and create transparency.
  10. Use a dedicated location to facilate the daily scrum meeting (same place and at the same time every workday).
  11. Keep things short: A daily scrum meeting should be fifteen minutes or less to keep focus and efficient.
  12. During the daily scrum meeting each member focus on: what has done yesterday, what will be done today, what issues may cacuse problems for progress.
  13. Always prepare a scrum meeting agenda to increase the effectiveness of the scrum meeting.
  14. Ask teammembers to come prepaired to meetings to ensure constructive participation and quick responses to questions or issues.
  15. Increase engagement during meetings by adding a small dose of humor.
  16. Create a distractions-free environment to host the meetings to improve focus and participation in the meeting.
  17. Use sepate meetings to discuss unsolved problems with only those members who are directly realted to the problem.
  18. Create an environment where team members proactively look for help.
  19. Ask teammembers to give each other timely constructive feedback.

Business management Best Practices examples

Business management Best Practices examples

  1. Engage workers;
  2. Set team expectations and be performanace driven;
  3. It is all about people;
  4. Initiatives must inspire shared insights;
  5. Reward effort;
  6. Having a clear process;
  7. Create a foolproof foundation;
  8. Be vulnerable;
  9. Stay committed;
  10. Implement continuou improvement thinking;
  11. Be transparent;
  12. Document the processes;
  13. Building for the future;
  14. Use data-driven decision making;
  15. Invest in the right people;
  16. Focus on excellent customer service;
  17. Seek clarity;
  18. Identify shared business values;
  19. Focus team effort;
  20. Schedule time for periodic evaluation;
  21. Managing without ego;
  22. Own the operation from start to finish.

Business management KPIs

  1. Sales Revenue
  2. Net Profit Margin
  3. Gross Margin
  4. MRR (Monthly Recurring Revenue)
  5. Net Promoter Score

Innovation management: 23 Best Practices examples

Innovation management: 23 Best Practices examples

  1. Allocate resources properly to support your strategy;
  2. Stimulate ideas by asking staff for input;
  3. Involve everyone in the organisation;
  4. Identify goals and stay focused;
  5. Embrace the opportunity mindset;
  6. Walk the talk;
  7. Plan for execution;
  8. Implement with speed;
  9. Cultivate a risk-taking culture;
  10. Develop organizational culture to support innovation;
  11. Create an innovative company culture;
  12. Collaborate with customers and strategic partners;
  13. Periodic evaluation of effectiveness of innovation programs;
  14. Apply continuou improvement thinking;
  15. Create an innovation strategy;
  16. Create value for your customers & stakeholders;
  17. Identify the best opportunities;
  18. Identify and remove barriers;
  19. Set up dedicated and cross functional innovation teams;
  20. Set-up research and technology networks;
  21. Incent and reward;
  22. Communicate results and milestones.

7 Innovation management KPIs

  1. Innovation rate = revenue share of innovations / total turnover * 100
  2. Innovation rate = number of innovations / number of products * 100
  3. The number of innovation projects started
  4. Number of new products launched in X amount of time
  5. Actual vs. targeted breakeven time for new products
  6. Revenue/profit growth from new products
  7. ROI of innovation activities