How to build the Mindset for Agile projects management:-

How to build the Mindset for Agile projects management:-

????? ???? ?????? ?????? ??????? ???????? ??????? ?? ???????? ??????? ??????? ??????? ?? ?????? ??? ????? ?????? ?????? ?????? ????????? ?? ???? ?????? ????????? ??? ??? ????? ?????? ??????? ?? ???? ????? ???????? ???????? ????????? ????????:-

**How you apply the values and principles of agile to your project, team, and organization:-

1- Be an active advocate for agile ideas in your organization and with your customers.

2- Help everyone around you develop an agile mindset through your own words and actions.

3- Educate and influence people around your organization to help them become more agile.

4- Use information radiators to show your progress and build trust and transparency.

5- Make sure everyone feels comfortable making mistakes without being blamed feeling threatened.

6- Always keep learning and experimenting in order to find new and better ways to work.

7- Collaborate with your teammates so knowledge doesn’t stay locked up with one person.

8- Help your team to self-organize and feel comfortable determining their approach to the work.

9- Use servant leadership to help everyone on the team to stay positive and keep improving.

**Using iterative and incremental development to deliver as much value as possible to stakeholders:-

10- Break the work down into minimal units and build the ones that deliver the most value.

11- Figure out what “Done” done means for each work item at the last responsible moment.

12- Use a methodology with practices and values that match the culture of the team and organization.

13- Break your product down into MMFs and MVPs and deliver the most valuable ones first.

14- Adjust the length of your iterations so that you can get frequent feedback from stakeholders.

15- Review the results of each iteration with stakeholders to make sure you’re delivering value.

16- Make sure your stakeholders are helping you prioritize the work so you deliver value quickly.

17- Build maintainable software and constantly fix technical debt to keep long-term costs down.

18- Operational and infrastructure factors can impact your project, so take them into account.

19- Meet with your stakeholders frequently and make corrections to the work and the plan.

20- Take the time to identify project risks, and add items to reduce risk to the backlog.

21- Your stakeholders’ needs and environment change all the time, so keep refining the backlog.

22- Make sure the team understands non-functional requirements like security and operations needs.

23- Continually inspect and test all of your artifacts (including the plan), use the results to adapt.

**Building trust with your project’s stakeholders by engaging and collaborating with them:-

24- The team identifies stakeholders and routinely meets with them to review the project.

25- Share all project information early and often with stakeholders so they stay engaged.

26- Help important stakeholders form a working agreement with each other to collaborate.

27- Stay on top of changes to your organization in order to identify new stakeholders.

28- Help everyone make better decisions more quickly through collaboration and conflict resolution.

29- Build trust with stakeholders by working with them to set a high-level goal for each increment.

30- Make sure everyone agrees on a definition of “done”, and what trade-offs are acceptable.

31- Make your project transparent by clearly communicating status, progress, roadblocks, and issues.

32- Give forecasts so stakeholders can plan, help them understand how certain the forecasts are.

**Helping the team collaborate, trust each other, and create an energized work environment:-

33- The team should work together to set ground rules that bring everyone together.

34- The team is committed to building up technical and interpersonal skills needed for the project.

45- Team members strive to be “generalizing specialists” who can contribute to all aspects of the project.

36- The team is self-organizing, and feels empowered to make important project decisions.

37- Teammates find ways to keep each other motivated and keep from demotivating each other.

38- The team should be co-located in the same office if possible, and use collaboration tools.

39- Distractions should be kept to a minimum to make sure the team achieves “flow”.

40- Everyone “gets” the project vision and understands how each piece of work contributes to it.

41- Measure project velocity and use it to figure out how much the team can do in each iteration.

**Evolve your project plan as you learn more about your project, stakeholders, and roadblocks:-

42- Iterate at every level of the project (daily meetings, sprints, quarterly cycles, etc.).

43- Be completely transparent with your stakeholders about how you plan the project.

44- Start out with broad commitments, and make more specific ones as the project unfolds.

45- Use retrospectives and your understanding of deliverables to change how and how often you plan.

46- Use an inspection-adaptation cycle to stay on top of scope, priority, budget, and schedule changes.

47- Collaborate to understand the ideal size of work items before taking velocity into account.

48- Don’t forget about maintenance and operations activities, which can affect your project plan.

49- Create initial estimates that take into account the fact there are still a lot of unknowns.

50- Keep refining your estimates as you learn more about how much effort the project will require.

51- Continue to update your plan as you get a clearer picture of the team’s velocity and capacity.

**Watch for problems and fix them, then improve how you work to prevent them from reoccurring:-

52- Give everyone on the team freedom to experiment and make mistakes.

53- Constantly watch for risks to the project, and make sure the whole team is aware of them.

54- When problems happen, make sure they’re fixed—or, if they can’t be fixed, set expectations.

55- Be completely transparent about the risks, problems, issues, and threats to the project.

56- Make sure risks and issues actually get fixed by including them in product and iteration backlogs.

**The team works together to keep improving the way that they do project work:-

57- Constantly look at the practices, values, and goals, and use that information to adapt the process.

58- Hold retrospectives frequently, and experiment with improvements to address issues you find.

59- Demonstrate working software at the end of every iteration, and genuinely listen to feedback.

60- Generalizing specialists are really valuable, so give everyone opportunities to improve their skills.

61- Use value stream analysis to discover waste, and make individual and team efforts to eliminate it.

62- When you gain knowledge from making improvements, share it with the rest of the organization