The “why” of the project. The goal is to have a compelling and clear vision for the effort.
Develop a subscriber management and billing platform usable in different types of utilities sector, integrated with Payconnect to leverage the payment methods and
-qualify further
This is the “What” of the project and it states what will be done in the project to achieve its higher purpose. This should include technical, business, product, and team objectives.
list benefits
- DCBMI additional security access from billing system to bucket server.
- Can monitor subscriber connection
- Can auto disconnect client up to OLT level
- User can monitor the bandwidth of the subscriber
- Productize billing system to be able to serve other subscriber based services
Other possible benefits
- Subscriber billing and status monitoring access .
Fintech
- Customer convenience.
- Multiple methods of payment
resilience
reduce complexity
operationalization mind set
Team Charter
- training on best practices
- test driven development
An assessment of how big the resources needed will be to deliver this service based on assessment of resources and organizational readiness for agile.
An assessment of how complex delivering this service will be based on assessment of scope and organizational readiness for agile.
Known/assumed customer needs, anticipated functional and non-functional requirements.
Executive/Stakeholder, project team organization chart (especially if there are multiple teams operating at the same time), organizational governance structures.
Space, equipment, people/roles, skillsets and capabilities, collaboration support, and tools. While you may not have names for all the teams that you will form for the project, you should have an idea of what roles you think will be needed.
- Office space at Dctech Micro Services, Shanghai St., Matina Aplaya
- Roles
- Product Manager
- Product Owner
- Scrum Master
- Dev Lead
- Business Analyst / IE
- Developers
- Product Support
- Testers
- DevOps
- Skill Sets Capabilities
- Determine needs and set product vision
- Scrum Methodology
- Tech Skills
- PHP, Laravel, MySQL DB, API Dev’t
- Long Term: Java, Spring Boot, Vue 3, Quasar, ELK Stack, Kafka
- DevOps: Repo Mgt, CI/CD, Operational
Strategies, methodologies, processes, tools and techniques the team will follow.
Success Criteria
What determines the success outside the solution itself? Should be concise, realistic, and directly measurable.
Ordering, importance, and trade-offs within the project objectives (simulates a high-level product roadmap or release plan) as well as relative to other projects the organization is sponsoring.
Defines where the product is headed and is tied to the vision and strategic goals. This is a key element that should be included.
- Payconnect API / Biller Center integration
- Productization features analysis
- Bucket Integration via SSH Workaround
- Subscriber mobile app / PWA
Schedule: Aug 4 - 10
Goals:
- Jibble integration with payroll
- Operationalize payconnect Integration with Infosystem
- Test HRMESS with dataconnect, poultrymax
Schedule: Aug 11 - 24
Goals:
- Operationalize billing center
- Payconnect Integration Study
- Jibble test set up with Dataconnect and Poultry Max Data
- Test HRMESS with dataconnect, poultrymax
Schedule: Aug 25 - Sept 7
Goals:
- Payconnect Integration for Validate and Confirm Transactions
- Set up Jibble owner account with PoultryMax organization and employee information
- Operationalize Pilot HRMESS for PoultryMax and DataConnect
- Documentation of the process flow for infosystem billing of new accounts
Schedule: Sept 8 - 21
Goals:
- Payconnect integration and end to end testing
- Billing System Enhancements
- Jibble rollout and import integration
- HR Enhancements
Schedule: Sept 22 - Oct 5
Goals:
- Payconnect Integration production RollOut
- prefixing of accounts for DataConnect
- production rollout
- Billing Pilot Prod Cutover
- Billing System Enhancements
- HR DC/PM Prod cleanup, turnover
- Jibble PM Prod RollOut preparation
- HRMESS System Enhancements
Schedule: Oct 6 - Oct 19
Goals:
- Bucket Integration Enhancement
- BillRun sandbox exploration
- Jibble PM and DC Production Cutover
Schedule: Oct 20 - Nov 02
Goals:
- Create documentation for dctech rollout of payconnect integration
- Create documentation to make the 711 merchant be that bank to deposit
- Present some of the alternative ways in biometric attendance for poultrymax
- Payroll parallel testing for Dataconnect
Schedule: Nov 3 - Nov 17
Goals:
- Router Backend for Billing system request VM and set up
- Appsheet for Receiving payment
- Dataconnect Payroll Parallel Testing 1st and 2nd Cycle
- Payroll Report Enhancements
Schedule: Nov 18 - Dec 1
Goals:
- Router Backend for Billing system Set up
- Billing Enhancements
- Dataconnect Payroll Parallel Testing 3rd Cycle
- HRMESS Kiosk Mode - employee ID
- Research face Recognition
- PWA Training
Schedule: Dec 2 - Dec 15
Goals:
- Billing Router Role out
- Move dctech infosystem to apollo server
- Billing Enhancements AR report
- Match infosystem and bucket server data
- Payroll Implementation
- Payroll Enhancements
Schedule: Dec 16 - Dec 26
Goals:
- Document dctech migration to Dataconnect server
- Centralize Billing Plan
- Lead developer from end to end
- Assigning personnel
- Can be use to any utility billing system
- auto sign up
- make the system modular
Leverage iNet features
- customer subscription
- provisioning
- activation
- billing
- support
- dcbmi
- disconnection
- ERP ?
- Subscriber mobile app / PWA
Integrations
- Payconnect API integration Services
- Asset Tracking
- What is the scope?
- What should be reused?
- DataConnect WorkConnect Integration with GIS
- Analytics Data Lake
- DCBMI features
- SSH Workaround
- Bandwidth Management
- Manage client IP
- Provisioning
- Disconnection up to OLT level
- Activate client connection
- Billing System adjustments
- Productization features
¶ Assumptions and Constraints
Restrictions, limits, boundaries that apply to the team, process, product, and/or schedule.
Top risks, known issues, and relevant organizational history that impacts readiness, specific points of uncertainty, and which includes mitigation plans for each.
Key stakeholder approval that authorizes the project and other necessary signatures.