weDevs Engineering Process

⌘K
  2. Home
  4. Docs
  6. weDevs Engineering Proces...
  8. Feature Development Process

Feature Development Process

  1. Ideation & Backlog Grooming:
    • Product Management: Identifies the need for a feature through customer feedback, market research, and internal insights.
    • The feature is discussed with stakeholders and added to the product backlog.
    • Features in the backlog are prioritized based on business needs, customer value, and technical feasibility.
  2. Feature Definition
    • Product Management: Drafts detailed feature requirements, user stories, and acceptance criteria.
    • Engage with Designers and Developers for feedback on feasibility and potential challenges.
  3. Design
    • Designers begin creating wireframes or mockups based on the requirements.
    • Collaboration between Design and Product Management is crucial here to ensure the designs align with the desired user experience.
    • High-fidelity designs and prototypes are finalized, considering feedback from PMs and developers.
  4. Sprint Planning
    • Teams review the product backlog, select top-priority items, and estimate the effort required.
    • The selected items form the sprint backlog.
    • Product Management ensures clarity on the user stories and acceptance criteria.
  5. Development
    • Developers start building the feature based on the designs and acceptance criteria.
    • Regular stand-ups (daily) ensure that blockers are addressed promptly.
    • Features are built in a separate branch, following best coding practices, including writing unit tests.
  6. Internal Review & Feedback
    • Once development reaches a milestone or is near completion, Designers and Product Managers review the implementation.
    • Feedback is provided, and necessary adjustments are made.
  7. QA & Testing
    • QA Engineers start their testing based on the acceptance criteria and design specifications.
    • Both manual and automated testing are employed.
    • Bugs are reported, and Developers address them. This process might go through several iterations
  8. Feature Documentation & Training
    • Product Managers and potentially dedicated technical writers should update documentation, release notes, and any necessary training materials.
  9. Deployment
    • Once the feature passes QA, it’s merged into the main codebase.
    • Continuous integration tools can help automate the build, test, and deploy process.
  10. Sprint Review & Retrospective
    • The team presents the completed feature to stakeholders during the sprint review.
    • In the retrospective, the team reflects on the sprint, discussing what went well and identifying areas for improvement.
  11. Release & Monitoring
    • The feature is released to customers.
    • Monitoring tools track the feature’s performance, usage, and any potential issues.
    • Product Management gathers feedback from users for future enhancements.
  12. Feedback Loop
    • Feedback from users, QA, and other stakeholders should continuously feed into the backlog, leading to iterations and refinements in subsequent sprints.