Why Every Job Seeker Should Have a Personal Website, And What It Should Include
IntellegoJobs – Current Job Opportunities, US Employment News, and Job Seeking Tips for the Bookkeeper, CPA, Programmer, Computer Hardware Engineer, Software Engineer, Computer Support Specialist, Systems Analyst, VoIP Engineer, Civil Engineer, Mechanical Engineer, High School Teacher, Middle School Teacher, Pharma Sales Rep, Sales Rep, Pharmacist, Physician Assistant, Physical Therapy Assistant, Registered Nurse, Pilot, and Truck Driver.
Business Analyst Community & Resources | Modern Analyst
RSS feeds for Business Analyst Community & Resources | Modern Analyst
What is the Blue Ocean Strategy?
Describe Porter’s Five Forces Analysis
Porter’s Five Forces was created by Michael E. Porter of Harvard Business School in 1979. Porter created his analysis framework in response to the well known SWOT analysis which he found to be lacking in rigor.
- Threat of new competition
- Threat of substitute products or services
- Intensity of competitive rivalry
- Bargaining power of customers (buyers)
- Bargaining power of suppliers
What is the BCG Matrix and how might you use it?
The BCG Matrix was developed by the Boston Consulting Group in 1986 in order to evaluate and analyze the business units and product offerings of corporations. Companies can use this simple 2 x 2 matrix as an analytical tool in portfolio analysis, strategic management, product management, and brand marketing.
The BCG Matrix plots business units or product offerings along two axis; the first is market growth, the second is market share.
What is a Minimum Viable Product?
A Minimum Viable Product (MVP) refers to a product that has just enough features to reasonably demonstrate its viability to a group of stakeholders in order to receive feedback. By greatly limiting the scope of the product to its absolute minimum feature set the product development team is able to limits costs and risks.
How does the Business Analyst role change on an Agile project compared to projects using other software development methodologies?
The role of the BA should actually change very little between different software development methodologies, although the tools and techniques used by the BA can vary according to the needs and attributes of any given project or development lifecycle.
The core responsibilities of a BA on a software development project include requirements elicitation, requirements analysis and requirements management – regardless of the project methodology. The type and format of requirements documentation are just tools, and a good BA has a wide range of tools at his or her disposal.
How are non-functional requirements defined and managed on Agile projects?
Non-functional requirements (NFRs) are typically defined as backlog constraints on an Agile project, and are managed as part of both product backlog and scrum backlog. They are revisited as part of the ‘Definition of Done’ for each iteration or sprint. If the system does not meet any given NFR, that NFR may spawn new backlog items such as refactors or performance enhancements.
What should be documented in a UI Design Pattern?
Though pattern descriptions vary somewhat, many pattern templates contain a set of common sections.
Primary Sections of a UI Design Pattern
Name: Should be concise yet descriptive (typically between two and four words in length) so that someone can find the pattern easily and reference it within discussions for clear communication amongst team members.
Description: A few lines briefly describing the pattern. Since short names are not always sufficient enough to clearly and uniquely describe the pattern a description is important. However, this is not where you will describe the pattern in great detail.
End User Requirement/Problem to Solve: Communicate what requirement or challenge will be solved by the pattern. What is the user trying to achieve?
When to Use/When Not to Use: It isn’t always obvious under which condition or within which context a pattern should be used. Here you can document when a pattern should be used and, equally important, when it should not be used.
Solution: Document the details of the pattern/solution including a detailed description of the user interaction. Include screenshots to help convey the pattern clearly as needed.
Comments: Capture any other comments that you feel are relevant to the reader.
Optional Sections of a UI Design Pattern
Depending on the needs of your team or organization you may choose to add some additional sections to your pattern template.
Examples of Past Uses: Including screenshots of past uses of the pattern along with a brief description can help the reader visualize the benefits of using the pattern.
Rationale for Use: Understanding why a particular pattern works so well can be invaluable when deciding whether to use one pattern over another. Detail out the specifics of the user experience and the direct benefits that they receive by using this pattern.
Implementation Specifications: If standards exist within your organization or team, consider accompanying the pattern with style guide information such as font family, font size, font weight, font color, table and cell spacing, and more. Or if the styles change based on the application or product being developed, provide a link to the style guide information.
Usability Research: Any specific feedback on how well the pattern works can be documented for future reference. Consider including feedback from UAT testers or your sales organization, but also don’t exclude feedback from developers and other testers.
Related Patterns: List other patterns that may solve a similar problem or patterns that work together to achieve a broader goal.
Pattern Variations: Document minor variations in the pattern that can be used. If the variations are significant enough, consider developing a separate but similarly named pattern. For example, “Tag Cloud 1” and “Tag Cloud 2”
Development Notes: Capture notes that help the development team implement the pattern. This may be a snippet of code or a link to a code library where the code for the pattern can be found.--
What is the One Metric That Matters and how can it be used to improve a product?
The One Metric That Matters (OMTM) is a minimalist approach that helps achieve this goal. OMTM is a mindset and guideline more than a rule. In practice, focusing on a single metric may be too restrictive to result in actionable data but this approach can be modified in a couple of useful ways. One is to identify a single metric for each facet of a product. Another is to focus on a single metric for a day, a week, or a month and optimize performance based on that single metric over that period of time.
Describe How Convergent and Divergent Thinking Can Be Used as a Problem Solving Technique?
Divergent and Convergent thinking when used together can help an analyst arrive at better and more creative solutions than he or she otherwise might have. Divergent thinking is the process of breaking a topic down and generating many ideas that branch out from the original concept while Convergent thinking is the process of focusing on a fewer set of ideas and evaluating them based on selection criteria.
What is Persuasive Design?
How would you conduct usability testing for a new custom-developed software system?
Usability testing is conducted in different ways over the software development life cycle:
Usability assessment is performed as part of unit and system testing as software is developed and released.
Usability testing is conducted at key development checkpoints, and may be part of an iterative user acceptance testing approach.
What are Scenarios within the context of User-Centered Design?
User-Centered Design (UCD) is an application design methodology which focuses on usability goals, user demographics, real-world environment, tasks, and workflow in the design of an application interface. During the analysis phase of UCD, two key stages are the User Analysis stage and the Workflow Analysis stage.
Describe the difference between univariate, bivariate and multivariate analysis?
Univariate analysis is the simplest form of data analysis where the data being analyzed contains only one variable. Since it's a single variable it doesn’t deal with causes or relationships. The main purpose of univariate analysis is to describe the data and find patterns that exist within it
Describe the Six Sigma methodology?
Six Sigma is a process improvement methodology. It is structured into 5 phases which can be iterated to continually improve key processes and deliver greater efficiencies and success within an organization. These 5 phases are Define, Measure, Analyze, Improve, and Control expressed as the acronym DMAIC (pronounced dee-may-ic). Six Sigma, being a process improvement methodology, views the entire world in terms of processes—processes that achieve goals, processes that act on data, etc.
Six Sigma DMAIC versus DMADV, what’s the difference?
The Six Sigma process improvement methodology defines the DMAIC and DMADV acronyms as follows.
DMAIC stands for Define, Measure, Analyze, Improve, Control. These 5 steps are used for improvement of existing processes to identify a candidate process, understand its current state of effectiveness, improve on the process, and manage its continued performance. This is described in more details under Describe the Six Sigma Methodology.
DMADV stands for Define, Measure, Analyze, Design, Verify. These 5 steps are used when a process doesn’t yet exist and needs to be designed to ensure it will meet customer specifications. It is also intended to be used when an existing process cannot be improved enough to bring it to within customer specifications and needs to be completely redesigned.
What is cognitive load and how does it impact product design?
Cognitive Load is a term that originates from the field of psychology. It refers to the amount of mental effort used in the working memory of a person. We all have limits to the amount of cognitive load that we can reasonably sustain. And it's understood that a large amount of cognitive load makes it more difficult for people to learn and remember important details or to make decisions and complete tasks.
What are some guiding principles or tenets of UI design?
Some of the guiding principles of UI design are: Usefulness, Consistency, Simplicity, Communication and Feedback, Error Prevention and Handling, Efficiency, Workload Reduction, Designer Judgment
What is a UI Design Pattern and what are its benefits?
UI Design Patterns are an important aspect of application and website usability and user experience. UI Design Patterns (also commonly referred to as Interaction Design Patterns) document and convey robust UI design solutions, that have proven to be successful over time, to common usability requirements. Properly applying UI Design Patterns ensures the UI designer that the application or website will be intuitive and its features and functionality robust.
What is Gherkin and how can it help the business analyst?
Gherkin is a structured natural language that is used by business analysts to specify how they want the system to behave for given scenarios. The Gherkin language is simple. It uses about 10 keywords (Given, When, Then, And, But, Scenario, Feature, Background, Scenario Outline, Examples) which allow the language to be read and parsed by an automation tool called Cucumber.
How would you convince management that a business analyst is needed within a team?
Answering a few key questions and summarizing the results can help you objectively present to management the need for a business analyst.
- What are the key tasks a Business Analyst would perform within your organization?
- How well is the team performing on each business analysis task?
- How much time/money is lost due to poorly performed Business Analysis tasks?
- Which tasks could the existing team improve on and which should be completed by an experienced business analyst?
- Perform a summary level cost-benefit analysis based on your findings.
Describe the life cycle of a User Story?
User Stories are used by agile methodologies to capture the functionality that a system or software should support. For details about what a user story is and how to write one reference What are User Stories.
Describe Artificial Intelligence and how it might impact the Business Analysis profession?
Artificial intelligence (AI) is an overarching term used to describe how computers are programmed to exhibit human-like intelligence such as problem solving and learning. This definition of AI is broad and non-specific which is part of the reason why the scope of AI can sometimes be confusing. As machines become increasingly capable of performing "intelligent" tasks, those tasks slowly become commonplace and as such are removed from the scope of what is generally accepted as artificial intelligence. This is known as the AI effect. A more precise definition might be any device that takes in information from it's environment and acts on it to maximize the chance of achieving its goal.
How might a business analyst use BPMN differently for Business Models than for Executable Models?
The origins of BPMN began in the area of executable models. That is, it was created to be precisely interpreted by workflow engines or business process management systems in order to automatically orchestrate how information, documents, or other workflow items are directed through a system. The benefit of an executable model is that it can be changed and immediately re-executed to establish a new workflow. At least, that’s the idea.
Once a system is developed is it reasonable to document changes with simple updates to screen mockups?
This question implies that the benefit of foregoing the creation of a more complete requirements specification document is a significant amount of time savings. But what might we be losing in the process.
Screen mockups alone don’t clearly document requirements. Instead, they reflect a decision made by the system designer to satisfy a particular requirement. Often when someone views the mockup or updated system they may think the requirement is obvious when, actually, they have misinterpreted the true requirement.
How do you prevent your application from being a confusing suite of features rather than one that meets a user's goals with ease?
Many applications are designed and completed only to result in a confusing suite of features that is difficult for the user to navigate. So how can an analyst avoid this pitfall. The answer is Design Thinking, also sometimes referred to as Human Centered Innovation or Human Centered Engineering.
Systems Analyst Jobs
Listed by State – Updated Daily
Powered by FirstRSS Plugin