Customer collaboration

Responding to change

  • To put change in perspective, change may occur because:

    • Changes in users and markets
    • A new feedback
    • Due to the cognitive limitations of human beings, it is impossible to completely and accurately describe the details of the needs needed for a long time in the future

  • Our real goal is to create successful products/apps, not complete project delivery! Change means opportunity!

  • Agile does not have a traditional requirements change process and builds a lightweight mechanism to respond to change.

    1. Delivery based on dynamic priority order
    2. Short iteration, delayed commitment

    VS is better than following a plan

  • Agile is not about not having a plan, it’s about not believing in big plans, making small plans (2 week iteration plans), and planning often;

  • Continue to do a good job in product planning, clear product development direction, is also conducive to maintaining balanced demand;

  • In each short iteration plan, try to keep requirements stable.

  • The shorter each iteration plan, the better the team’s ability to respond quickly to change;

The agile manifesto

The 12 Principles of the Agile Manifesto

  1. Our most important goal is to satisfy our customers by consistently delivering valuable software early.
  2. Embrace changes in requirements, even late in development. To master change in a flexible process for customer competitive advantage.
  3. Delivering working software frequently, a few weeks or a month or two apart, tends to take shorter cycles.
  4. Business, product, and developer must work together, every day of the project;
  5. Motivate individuals and build teams around them. Provide the environment and support needed, complemented by trust, to achieve goals.
  6. Face-to-face conversations are the most effective and efficient way to convey information, both inside and outside the team;
  7. Working, valuable software is the primary measure of progress.
  8. Promote a sustainable development pace. Team leaders, developers, and requirements should be able to work together to keep the pace steady;
  9. Agility is enhanced by a relentless pursuit of technical excellence and engagement;
  10. Based on simplicity, it is the art of minimizing unnecessary work.
  11. The best architectures, requirements, and implications come from self-organizing teams.
  12. The team periodically reflects on how it can be more effective, and then adjusts its behavior accordingly for continuous improvement.

The 12 principles of the Agile Manifesto are often examined: Are we really Agile?

Agile is not a set of processes, agile is management principles, and a set of practices for creating great software! Agile is about developing products, not delivering projects!

Agile requires discipline and ability for continuous improvement!

Responsibilities of DMS and PO in Agile development

Delivery experience DM (I want to make sure the team is excellent)

  1. Cultivate team members, guide the formulation of team contract, and form a team culture of trust, development, equality, respect, learning and collaboration;
  2. Cooperate with DDA to lead or promote the timely and effective implementation of profile related activities to ensure the quality of profile design;
  3. Lead the cross-functional agile team to operate efficiently and continuously in an agile manner, develop reasonable iteration plans, effectively organize key activities, and ensure delivery quality;
  4. Establish communication channels between management, business side, PO and team, eliminate communication barriers;
  5. Work with PO on iteration planning, manage product backlog, especially technical story and debt, pre-research work items;
  6. Transparent management of team delivery schedule, risks and dependencies, timely coordination and resolution of obstacles;
  7. Work with other related teams to coordinate requirements, design and task scheduling and integration across teams;
  8. Collect and analyze process and result measurement data to drive continuous improvement of team;

Product Manager PO (I want to make sure this product is successful)

  1. Align product vision and goals with business, customers and company stakeholders;
  2. Conduct in-depth research on users and customers to understand and define the problems and values to be solved;
  3. Lead or solution team to develop product solutions and prototype design to ensure quality requirements;
  4. Formulate the evolution route of the product, and carry out the iterative version planning of the product;
  5. Split and define user stories, write acceptance criteria, manage product backlog and prioritize stories and other work items in the backlog;
  6. Support team in efficient and high quality delivery, timely explain and clarify team questions on requirements and product design;
  7. Organize business acceptance, or organize a team to demonstrate to business or users, collect feedback as soon as possible;
  8. Design key operational indicators, collect and analyze data, verify the real effectiveness of products and requirements, identify user or business problems from data feedback, and generate ideas for further improvement.

How to be a good PO?

  • Basic skills: domain knowledge, communication and guidance, organization and coordination
  • Basic professional skills: exploration and research, product design, agile requirements
  • Advanced professional abilities: business planning, product operation

Read more [Agile Knowledge], [Agile Transformation Experience], Practices… If you are interested in our products, you can visit our official website, Jingzhou R&D Management platform for trial understanding