STAYING AGILE 5 Best Practices in Software Project Management

Get Started. It's Free
or sign up with your email address
Rocket clouds
STAYING AGILE 5 Best Practices in Software Project Management by Mind Map: STAYING AGILE 5 Best Practices in Software Project Management

1. Establishing the ‘Why’:

1.1. Begin every project with a strategy sprint

1.2. Focused on identifying

1.2.1. Which pain points will be solved

1.2.2. Which unique experience or service the proposed product would support

1.3. Define vision and communicate it to the team!

1.4. 5-Day Strategy Sprint Agenda

1.4.1. Day 1: Map out the pain point or need for the product

1.4.2. Day 2: Establish existing competing solutions

1.4.3. Day 3: Use the initial ideas to establish a testable hypothesis

1.4.4. Day 4: Create a rough product prototype

1.4.5. Day 5: Test the prototype on prospective end-users (i.e. real human beings)

2. Planning to Perfection

2.1. Provide a Realistic Project Scope & Budget

2.2. Establish an Agreed Project Scope

2.2.1. Create a project mind map for each new client during the project consultation stage

2.2.2. Align expectations

2.2.3. Ensure all key features have been considered in the price

2.3. Use pricing process based on the cone of uncertainty

2.3.1. Help client make informed decisions

2.3.1.1. proactive project updates

2.3.1.2. weekly client meetings

3. Customer Values

3.1. Engage with client and user feedback at every iteration

3.2. Key steps for achieving rapid and regular end-user insight

3.2.1. Access

3.2.2. Listen

3.2.3. Communicate

3.3. Integrate User and Client Feedback within Sprints, Using Scrum

3.4. Create a Physical Scrum Wallboard

3.5. Manage Project Scope via Online Collaboration Tools

4. Collaborating Cross-departmentally

4.1. Enable constant communication between your business and development teams

4.1.1. "Any Agile approach used by the development team must support all business needs and address all stakeholder concerns" - Dorian Simpson

4.2. Prevent Siphoning with Online Communication

4.2.1. Find a solution that is easy enough to use for everyone

4.2.2. Create a bridge between different departments, enabling everyone to remain on the same page with project progression.

5. Sustainable Productivity

5.1. Achieve team efficiency long-term

5.2. Review Productivity via Sprint Retrospectives

5.2.1. Client satisfaction

5.2.2. Cycle time of particular backlog items

5.2.3. QA kickback rate

5.3. Use Kanban boards to assess where bottlenecks are being created

5.4. Create sustainable workflows

5.4.1. Ensure that your team is not overloaded with features within each Sprint

5.4.2. Be consistently open and honest with clients to ensure that not too many features are added

6. Resources

6.1. Download the Free White Paper

6.2. Manifesto for Agile Software Development

6.3. Collaborative Task Management for Teams