Scribd
Upload
19 views5 pages

Value Stream Map

The document outlines Wise Software Corp's software development process through a Value Stream Map (VSM), detailing seven phases from customer request gathering to maintenance and support. Each phase includes process owners, tools used, stakeholders, lead and process times, as well as potential inefficiencies. Key takeaways highlight a total lead time of approximately 33 days and suggest optimizations such as automating testing and improving code review efficiency.

Uploaded by

huy huy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
19 views5 pages

Value Stream Map

The document outlines Wise Software Corp's software development process through a Value Stream Map (VSM), detailing seven phases from customer request gathering to maintenance and support. Each phase includes process owners, tools used, stakeholders, lead and process times, as well as potential inefficiencies. Key takeaways highlight a total lead time of approximately 33 days and suggest optimizations such as automating testing and improving code review efficiency.

Uploaded by

huy huy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Value Stream Map (VSM) – Wise Software

Corp’s Software Development Process


1. Customer Request & Requirement Gathering
Purpose: Capture and refine customer requirements for new features or bug fixes.

Process Owner: Product Manager, Business Analyst


Tools Used: Jira, Confluence, Google Docs, Miro (brainstorming)
Stakeholders: Customers, Product Owners, Business Analysts, Development Team

Process Breakdown:

1. Customer submits a request via email, support portal, or ticketing system.


2. Business Analyst (BA) reviews the request, clarifies ambiguities, and gathers additional
details from the customer.
3. BA creates a User Story detailing expected functionality and constraints.
4. The Product Manager reviews and prioritizes the request in the backlog.
5. The request is validated and approved by stakeholders before moving to the next phase.

Lead Time: 5 days


Process Time: 2 days
Potential Inefficiencies:

 Delays in customer response for clarification.


 Poorly defined requirements leading to rework.
 Mismatch between business needs and technical feasibility.

2. Planning & Design


Purpose: Convert business requirements into a structured, feasible technical solution.

Process Owner: Product Manager, UX Designer, Software Architect


Tools Used: Figma, Lucidchart, UML diagrams, ERD tools
Stakeholders: Product Team, Software Architects, UX/UI Designers, Developers

Process Breakdown:

1. Technical Feasibility Analysis – Evaluate complexity, dependencies, and risks.


2. UX/UI Design – Create wireframes, prototypes, and UI/UX flows for approval.
3. System Architecture Design – Define system components, APIs, and database schemas.
4. Sprint Planning & Task Breakdown – Convert high-level requirements into detailed
tasks with estimations.

Lead Time: 4 days


Process Time: 3 days
Potential Inefficiencies:

 Frequent design changes causing delays.


 Poor collaboration between designers and developers.
 Unclear scope leading to misalignment between teams.

3. Development (Coding & Unit Testing)


Purpose: Implement the feature based on the approved design, ensuring code quality and
functionality.

Process Owner: Development Team


Tools Used: VS Code, IntelliJ, GitHub, GitLab, Jenkins, Docker
Stakeholders: Developers, Tech Leads, QA Engineers

Process Breakdown:

1. Developers pull the assigned tasks from the backlog and begin coding.
2. Each feature is implemented with unit tests to validate correctness.
3. Peer Code Review – Developers submit a pull request (PR) for review.
4. Once approved, the code is merged into the main branch.
5. Continuous Integration (CI) – Automated testing and build verification.

Lead Time: 10 days


Process Time: 8 days
Potential Inefficiencies:

 Debugging delays due to missing unit tests.


 Bottlenecks in code reviews slowing down merging.
 Dependency on third-party APIs causing delays.

4. Integration & System Testing


Purpose: Verify system functionality, performance, and security in a controlled environment.
Process Owner: QA Team
Tools Used: Selenium, Postman, JMeter, SonarQube
Stakeholders: QA Engineers, Developers, Product Owners

Process Breakdown:

1. Deployment to Staging – The new build is deployed to the test environment.


2. Functional Testing – Verify if the software works as expected.
3. Performance Testing – Test the system under heavy loads to assess stability.
4. Security Testing – Identify and resolve vulnerabilities.
5. Integration Testing – Ensure seamless interaction between modules.
6. Report bugs and issues, sending them back to development if necessary.

Lead Time: 6 days


Process Time: 4 days
Potential Inefficiencies:

 Redundant test cases increasing testing time.


 Bugs detected late, requiring significant rework.
 Lack of test automation slowing down regression testing.

5. User Acceptance Testing (UAT)


Purpose: Ensure that the software meets business requirements before production deployment.

Process Owner: Business Team / End-Users


Tools Used: UAT checklist, Jira, TestRail
Stakeholders: Business Users, Product Owners, QA Team

Process Breakdown:

1. The product is deployed to the UAT environment for real-world testing.


2. Business users test the software using real scenarios.
3. Feedback is collected, and minor adjustments are made.
4. If approved, the software moves to the release phase.

Lead Time: 5 days


Process Time: 3 days
Potential Inefficiencies:

 Limited user availability for testing.


 Incomplete test coverage leading to missed defects.
6. Deployment & Release
Purpose: Deploy the software to production with minimal downtime.

Process Owner: DevOps Team


Tools Used: Jenkins, Kubernetes, Ansible, AWS/GCP/Azure
Stakeholders: DevOps, Developers, Business Owners

Process Breakdown:

1. Final Regression Testing – Ensure all functionalities work correctly.


2. Database Migrations – Apply any schema changes.
3. Production Deployment – CI/CD pipeline automates the release process.
4. Monitoring & Rollback Plan – Track system health and prepare rollback options.

Lead Time: 3 days


Process Time: 2 days
Potential Inefficiencies:

 Unexpected environment issues causing rollback.


 Manual deployments leading to errors.

7. Maintenance & Support


Purpose: Handle customer support requests, fix bugs, and optimize the system.

Process Owner: Support & Maintenance Team


Tools Used: Zendesk, Freshdesk, Log Monitoring Tools
Stakeholders: Support Engineers, Developers, Customers

Process Breakdown:

1. Ticket Handling – Categorize and prioritize incoming support requests.


2. Issue Resolution – Fix bugs and apply hotfixes when needed.
3. Continuous Monitoring – Track logs and performance metrics.
4. Software Optimization – Regular updates and performance tuning.

Lead Time: Ongoing


Process Time: Varies by issue complexity
Potential Inefficiencies:

 Repeated bugs due to lack of root cause analysis.


 Overloaded support team delaying response times.
Process Metrics Overview
Phase Lead Time (Days) Process Time (Days)
Customer Request & Requirement Gathering 5 2
Planning & Design 4 3
Development (Coding & Unit Testing) 10 8
Integration & System Testing 6 4
User Acceptance Testing (UAT) 5 3
Deployment & Release 3 2
Maintenance & Support Ongoing N/A

Key Takeaways & Improvement Opportunities:


 Total Lead Time: ~33 days
 Total Process Time: ~22 days
 Major Bottlenecks:
o Delays in customer response during requirement gathering.
o Lengthy review cycles in development and testing.
o Manual processes in testing and deployment.

Recommended Optimizations:

Automate testing (e.g., unit, regression, performance).


Improve code review efficiency with better tooling and guidelines.
Enhance CI/CD pipelines for faster, error-free deployments.
Implement predictive monitoring to reduce post-deployment issues.

This detailed Value Stream Map (VSM) provides a comprehensive overview of Wise
Software Corp’s software development process. Let me know if you need further refinements!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy