Requirements

• Bachelor’s Degree in Computer Science or a related discipline or an equivalent work experience. • Project management knowledge. • Working with Microsoft Office. • Familiar with software engineering methodologies, concepts and development process. • Familiar with computer networks. Knowledge of NGN concept is a bonus. • Minimum of two years in the engineering and operations of information technologies. • Familiarity with the concepts of database. (MS SQL) • Troubleshooting experience including root cause analysis, debugging utilities, etc. • Participates in testing and installing new software releases and application system upgrades and validates functionality following changes. • Must be self-motivated with the ability to work alone or with limited supervision. • Knowledge of ITIL and change management methodologies. • Ability to work well collaboratively with other team members, exercising good communication skills. Personal Skills: • Leadership: A product owner has to be a leader from the beginning of the project. They must provide a strong voice to inform the decisions around what (and what not) to build, identify market gaps and customer needs, and provide clear, actionable feedback to guide development teams. The product owner is also a developer of the project, the vision, and the team. And they must demonstrate commitment to the product by being available and engaged throughout the development cycle. • Decision-Making: The product owner must be able to make decisions quickly and with authority. After all, this person has deep knowledge of the needs of customers and stakeholders, including domain knowledge of the market and the environment for the product. • Communication: A product owner has to build a team, as well as work with internal and external stakeholders. It’s critical to be able to share the vision, focus the work, and communicate with various constituencies. The product owner also connects the people with the information. Developers may need to talk directly to users to get the details they need about the code they are writing. Stakeholders may need to talk with the business analyst to gain insight about the customer value of the product. You don’t have to be the expert in every conversation, but the product owner is the knowledge broker. • Delegation: While the product owner is responsible for the overall output, they cannot be the only person doing the work. The product owner has to know which duties fit best with the skills of each team member and ensure smooth collaboration. They provide the oversight and finds resources to ensure the job is complete. • Conflict Resolution: No project proceeds without some disagreements along the way. In the words of Lowell Lindstrom, a Certified Scrum Trainer® and one of the early pioneers in Agile software development, "If you can't handle conflict, you're in the wrong game." Product owners have to stop disputes and find solutions. Some conflicts, however, cannot be resolved at the product owner level. Knowing when a dispute needs to be sent up the chain of command is as important as knowing what to resolve. • Stakeholder Management: This can make the difference between progress and chaos. A successful product owner focuses on efficient workflows, clear expectations and milestones, and open and frequent communication. This ensures that the team identifies and resolves issues quickly and meets objectives so that development stays on schedule. • Product and Development Experience: While a product owner doesn’t necessarily need to be a trained software engineer, understanding the basic processes involved in software development is critical to developing realistic schedules, workflows, and stakeholder expectations. Experience with existing products or the overall product category is essential to recognizing the market and audience needs. • Customer and Market Insight: The product owner provides the core information that informs the features, pricing, sales forecasts, marketing strategies, and more. The product owner’s business savvy will help them make decisions during the development process. To please customers, the product owner must be able to meet their needs and act as the chief storyteller of the value of the product. • Tactical Skills: While many of their skills focus on leadership and strategic thinking, a successful product owner also needs tactical expertise. This covers the day-to-day management of what will get done and by when. • Technical Skills: Product Owner can review Conflicts in Implemented Code, Data Provider Queries and Documents of System Analyze then Provides Solutions of Any Problem in fault way of business method and development.