Recent Posts

Pages: 1 ... 8 9 [10]
Business Analyst Concepts Discussion / Re: Use case specification
« Last post by 1200182002 on April 11, 2020, 02:28:51 pm »
dependencies are about the order or sequence of tasks. Whereas constraints are limitations to the project, such as the limited availability of resources like time and funds.
A SWOT analysis is one element of a strategic plan. When plotting out a strategic plan, one of the most important details to explore is how the company will make decisions and manage competition. Therefore a SWOT is a business planning tool while a strategic plan is an overall business proposal for how the company will find its success. Also, a SWOT focuses on a company’s current position while a strategic plan forecasts into the future.
Business Analyst Concepts Discussion / Re: Scrum
« Last post by 1200182002 on April 11, 2020, 02:25:11 pm »
In Scrum, there are three roles: Product Owner, Development Team, and Scrum Master. Together these are known as the Scrum Team

Scrum Master: Roles and Responsibilities
The Scrum Master helps the product group learn and apply Scrum to achieve business value. The Scrum Master does whatever is in their power to help the Team, Product Owner and organization be successful. The Scrum Master is not the manager of the Team members, nor are they a project manager, team lead, or team representative. Instead, the Scrum Master serves the Team; he or she helps to remove impediments, protects the Team from outside interference, and helps the Team to adopt Agile development practices. He or she educates, coaches and guides the Product Owner, Team and the rest of the organization in the skillful use of Scrum.
Scrum Master ensures everyone follows the practices prescribed by Scrum.

A Scrum Master is a facilitator and Servant Leader who encourages and demands self-organization from the development team.
A Scrum Master enables close cooperation across all roles and functions, addresses resource issue and disobedience of scrum practices.
A Scrum Master protects the team from external and internal distractions.
A Scrum Master removes impediments so the team can focus on the work at hand and follow scrum practices.
A Scrum Master is not typically a manager or lead, but he is an influential leader and coach who does not do direct command and control.

Scrum Product Owner: Roles and Responsibilities
The Product Owner is responsible for maximizing return on investment (ROI) by identifying product features, translating these into a prioritized list, deciding which should be at the top of the list for the next Sprint, and continually re-prioritizing and refining the list. The Product Owner has profit and loss responsibility for the product, assuming it is a commercial product. Product Owner in Agile is like a spokesperson for customer and needs to represent them,

A Product Owner owns the Product backlog and writes user stories and acceptance criteria.
A Product Owner is responsible for prioritizing the Product Backlog is prioritized and decides the release date and the content.
A Product Owner accepts or rejects product backlog item.
A Product Owner has the power to cancel the Sprint, if he thinks the Sprint goal is redundant.
A Product Owner is the one who is responsible for the Return on Investment (ROI) of the product.

Development team: Roles and Responsibilities
A Development Team is a collection of individuals working together to develop and deliver the requested and committed product increments. It comprises of cross-functional members who are capable of achieving the sprint goals. This could include software engineers, architects, programmers, analysts, system admins, QA experts, testers, UI designers, etc.

The Development Team builds the product that the Product Owner indicates: the application or website, for example. The Team in Scrum is “cross-functional”
The Development Team includes all the expertise necessary to deliver the potentially shippable product each Sprint
The Development Team is self-organizing, with a very high degree of autonomy and accountability.
The Development Team decides how many items to build in a Sprint, and how best to accomplish that goal.
The Development Team is a cross functional, small and self-organizing team which owns the collective responsibility of developing, testing and releasing the Product increment.
The Development Team may not appoint any team lead since decisions are taken collectively by the team.
Business Analyst Concepts Discussion / Re: use case actors
« Last post by 1200182002 on April 11, 2020, 02:22:00 pm »
Primary Actor: a user whose defined user goal and is fulfilled by the system

The primary actor of a use case is the stakeholder that calls on the system to deliver one of its services. It has a goal with respect to the system – one that can be satisfied by its operation. The primary actor is often, but not always, the actor who triggers the use case.
Supporting Actors: a user who provides a service (e.g., information) to the system.

A supporting actor (also known as a secondary actor) in a use case in an external actor that provides a service to the system under design. It might be a high-speed printer, a web service, or humans that have to do some research and get back to us.
identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritize, review, estimate and validate the users.
Business Analyst Concepts Discussion / Re: Basics of Gap Analysis
« Last post by 1200182002 on April 11, 2020, 02:17:45 pm »
A gap analysis is process that compares actual performance or results with what was expected or desired. The method provides a way to identify suboptimal or missing strategies, structures, capabilities, processes, practices, technologies or skills, and then recommends steps that will help the company meet its goals.

By comparing the current state with the target state, companies, business units, or teams can determine what they need to work on to make their performance or results better and get on the right path quicker
A functional requirement defines a system or its component whereas a non-functional requirement defines the performance attribute of a software system. ... Types of Non-functional requirement are Scalability Capacity, Availability, Reliability, Recoverability, Data Integrity, etc
Business Analyst Concepts Discussion / Re: BA proportion in projects
« Last post by 1200182002 on April 11, 2020, 02:08:28 pm »
1. 15% of the SDLC/ total project time shoiuld be allocated to the BA
2. 12% to 16% of team size should be BAs
Business Analyst Concepts Discussion / Re: gantt charts
« Last post by 1200182002 on April 11, 2020, 02:06:30 pm »
A Gantt chart is a type of bar chart that illustrates a project schedule. This chart lists the tasks to be performed on the vertical axis, and time intervals on the horizontal axis. The width of the horizontal bars in the graph shows the duration of each activity.
Business Analyst Concepts Discussion / Re: gold plating
« Last post by 1200182002 on April 11, 2020, 02:04:25 pm »
gold plating means the addition of any feature not considered in the original scope plan or product description at any point of the project.
Pages: 1 ... 8 9 [10]