Hints and Tips for a Business Analyst

•

1 like•2,185 views

The document provides hints and tips for business analysts (BAs) on various stages of a project. It discusses important considerations when first assigned to a project like ensuring clear objectives and identifying an executive sponsor. It emphasizes the importance of planning before starting a project to avoid failure. Specific planning elements mentioned include stakeholder analysis, developing a business analysis workplan and allocating sufficient time to requirements discovery. During a project, the document notes things BAs should focus on like workshops, mentorship and requirements reviews. It also flags things to watch out for such as assumptions about domain knowledge. After a project, it discusses sign-off challenges, conducting post-implementation reviews and learning lessons around requirements quality and defects.

©

Hints and Tips for the BA?

Robin Grace
Principal Consultant
Business Analysis Practice

All material in this presentation is, unless otherwise stated, the property of
IndigoCube. Copyright and other intellectual property laws protect these
materials. Reproduction or retransmission of the materials, in whole or in part,
in any manner, without the prior written consent of the copyright holder, is a
violation of copyright law.
Contact information for requests for permission to reproduce or distribute
materials are listed below:
info@indigocube.co.za

Agenda

• When you are assigned to a Project
• Before you Start a Project
• During The Project
• After the Project

When you are assigned to a Project

Most projects fail before they are started,
because of poor objectives.

When you are assigned to a Project

Project Objectives
• Time frames
• Measurable
• Business Value

P=R-C
Why is this project being done?

When you are assigned to a Project

Executive Sponsor?

Before you Start a Project

No Planning, is planning for failure.

Before you Start a Project

Planning
One Size Does Not Fit All
Stakeholder Analysis (RACI)
Business Impact
Business Analysis Workplan
Not enough Time Allocated to the
Requirements Discovery Process

Before you Start a Project

Stakeholder
Stakeholder
Stakeholder
Analysis
Stakeholder
Analysis
Stakeholder
Analysis
Worksheets
Analysis
Worksheets
Analysis
Worksheets
Worksheets
Worksheets

Project
Overview
Worksheet
Deliverable
Deliverable
Deliverable
Worksheets
Deliverable
Deliverables Worksheets
Deliverable
Worksheets
Worksheets
List Worksheets

Business
Impact
Worksheet

Business
Summarized PM Project
Analysis
Plan (WBS)
Work Plan

Before you Start a Project

The Result of Good Planning
What
When
Who
Why
How
Result

Not enough time allocated to the
requirements discovery process

During The Project

Things You We Aren’t Doing Enough
•Workshops
•Mentorship
•Peer Reviews
•Requirements Reviews

Things to Look Out for During The Project

• What is a System ?

• Understand What a System is
 Business Rules Wrap in Technology

Things to Look Out for During The Project

• Domain Knowledge Assumptions
• Not Involving the Technical Team Early
• Mixing Solution Requirements with
Business Requirements

After the Project

Sign Off Blues
Post Implementation Review
Lessons Learned
What caused the Defects
Where the Requirements Weren't Good
Enough

Questions

The IndigoCube Business Analysis Practice is committed
to assisting clients to perform Business Analysis better
through solutions in
Business Analyst Assessment
Methodology Provisioning
Creation
Customisation
Implementation
BA Skills Development

Contact information info@indigocube.co.za
robin@indigocube.co.za

What's hot

Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...

Scrum Bangalore

The document discusses scaling Kanban across teams and organizations. It describes expanding Kanban in three dimensions: width, height, and depth. Width involves extending the workflow upstream and downstream. Height involves linking different levels of work from portfolio to personal tasks. Depth involves visualizing and managing interdependent services across shared resources. The document provides examples and recommendations for coordinating Kanban at scale, including common metrics, managing work in progress limits, and benefits of scaling Kanban such as increased flow and throughput.

DevOps: The Key to IT Performance

Nicole Forsgren

Dr. Nicole Forsgren will present the latest research that uncovers what really drives business outcomes of market share, profitability, and productivity as well as DevOps transformation awesomeness... Hint: these need the right mix of IT, culture, and practice, and include continuous delivery and lean management. This exciting research was done with Jez Humble and Gene Kim, and is promising exciting new projects in the space.

Agile foundation and agile myths

Dennis Stevens

The document compares predictive and agile software development approaches. It outlines that predictive approaches rely on upfront planning and strict adherence to plans, which can be unrealistic given the inherent uncertainties in software projects. Agile approaches separate estimates from execution, focus on frequent delivery of working software, and emphasize adapting to changes and feedback. While myths exist that agile means no planning, documentation, commitments, processes, or roles like project managers, when applied properly agile can dramatically improve an organization's ability to deliver working software.

Agile 101

digitalpurview

This document provides an introduction to Agile methodology, describing its principles and frameworks as an alternative to traditional waterfall project management. It outlines key differences such as iterative delivery of working software versus a single release at the end, as well as emphasis on collaboration, responding to change, and individual/team empowerment over rigid plans and processes. The Agile manifesto values individuals, working software, customer collaboration, and response to change over comprehensive documentation and contract negotiation. Common Agile frameworks like Scrum, Kanban, and XP are also introduced.

Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...

Scrum Bangalore

The document discusses agile architecture and how architecture can support agile development. It defines agile architecture as one that allows quick replacement of details and is easy to verify. An agile architecture enables the principles of the Agile Manifesto by allowing for quick change and being verifiable at any point. Traditional architecture focuses on rules and limitations, while agile architecture is needed to support rapid development, continuous delivery of value, and managing change and complexity. The document outlines practices of agile architecture including having architecture as part of the scrum team and modeling and documenting in an agile fashion. It also discusses roles like the agile architect and characteristics like understanding stakeholders and having a big picture view.

Speed Dating for Project Management Software

Margot

This document summarizes a presentation on selecting project management software for libraries. It discusses common project management principles and challenges libraries face in selecting software. It provides case studies on libraries that used Trello and other tools. The presentation evaluates Microsoft Project, Basecamp, Jira, and Trello for their fit with different project needs and budgets. It concludes that the right software depends on a library's specific projects and team size, and that tools alone don't ensure effective project management.

Agile 101

beLithe

Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.

cPrime FBI Agile Success

Cprime

Richard Wilburn - Lean Truth

AgileNZ Conference

Agile and looking to optimise your processes? Or tired of conflicting information within your project teams causing excessive development rework? Maybe you want to get a feel for the size of rework happening in your projects? In this session, we will look at how to detect inefficiencies in the software development process and, as we journey deeper, how to remove inefficiency through the adoption of a single source of truth. In our experience, a single source of truth is the goal of all companies, regardless of the company growth profile and at all levels of business, ranging from executive down to production level. We will elaborate on what a single source of truth is and how you can employ such a concept in your organisation with practical examples, based on commercially used best practices. No punches pulled!

Agile Software Development proposal for UIW 3

Sajjad Mansoor

The document proposes adopting an agile software development process to address current project problems like siloed work and lack of transparency. It summarizes the agile manifesto and Scrum framework, including roles like product owner and Scrum master. An implementation plan is outlined, with activities like sprint planning, daily stand-ups, and retrospectives. Metrics are suggested to measure velocity, defects, testing coverage. Management support is requested to shift mindsets to agile, provide training, tools, and accept that initial sprints may not go smoothly as the team learns.

Career Paths for IT Graduates

Dotitude

Agile 101 Agile Essentials In The Scrum Framework

Vernon Stinebaker

The document provides an overview of agile principles and the Scrum framework. It discusses the values of agile like prioritizing customer satisfaction, responding to change, and valuing individuals. The principles behind agile like welcoming changing requirements, frequent delivery of working software, and self-organizing teams are also outlined. Finally, it briefly introduces Scrum roles, ceremonies, and artifacts.

Fundamentals of Agile

Zülfikar Karakaya

The document discusses fundamentals of agile development including the agile manifesto and its 12 principles. It emphasizes values such as individuals and interactions, working software, customer collaboration, and responding to change. It also discusses agile processes like Scrum and Kanban, continuous improvement through inspection and adaptation, and techniques like test-driven development, pair programming, and continuous integration to enable regular rapid feedback. Finally, it notes that while agile is popular, the real question is whether it will make teams more successful in delivering value to customers on time and under budget.

Ba ,agile and career prospects

tony_aim83

Conducting Agile Retrospectives

Intelliware Development Inc.

Software Project Management - Introduction and fundamentals

Emanuele Della Valle

Are you Agile enough?

Orange and Bronze Software Labs

Butch Landingin, CTO of Orange & Bronze Software Labs, talks about the Agile Methodology for the Philippine Software Industry Association's Enablement Seminar on April 27 at the AIM. About O&B: Orange & Bronze is an offshore product and software development firm in the Philippines, is one of the first companies in Asia to use and advocate Agile Software Development, and has been using it since our inception in 2005, back when Agile was still an emerging movement. O&B offers training courses for Agile with Scrum and XP - these classes were developed and are taught by some of the Philippines' well-known and respected Agile / Scrum coaches and practitioners, and uses the format trusted by some of the best companies in the Philippines.

Agile and DevOps Transformations in Large Organizations

TechWell

Many large scale organizations experience significant challenges as they pursue agile and DevOps transformations. They embark on adopting agile practices yet fail to reap the benefits of continuous release and delivery. Siraj Berhan explores common challenges—people, processes, technology, and operations—in the agile journey of large-scale organizations. Siraj explores a project suitability assessment tool for evaluating as well as mitigating risks specific to agile delivery, incorporating a time-and-material funding model, and maintaining a cross-functional self-managing team with a generalist-specialist attitude. Siraj discusses moving from a test-last mentality to a test-driven culture with a heavy emphasis on automation that supports continuous integration, release, and delivery. He offers suggestions for promoting collocated development model to maximize the team’s agility and velocity while leveraging the usage of collaboration tools to its fullest. Explore ways to revamp engineering skillsets across the enterprise with practices and approaches that enable agility. Learn twelve helpful tips for getting started and additional advice for scaling your agile and DevOps journey.

Requirements hangout

Agile Arena

دي الAgenda: 1. تحديات الrequirements 2. ازاي تفكر Agile في شغل الrequirements 3. دور Product Onwer 4. ازاي نكتب User Stories 5. يعني ايه BackLog Refinement الhangout ده بيتعمل كل اسبوعين مع جروب agile بالعربي عشان نحاول نوصل المعلومة بشكل تفاعلي فيه مناقشات اكتر https://www.facebook.com/groups/Agile.bel3araby/ الhost انا Mona Shokrof , بشتغل Agile coach and trainer في Agile Arena ده الaccount بتاعي علي linked in https://www.linkedin.com/in/monashokrof اللي حابب يسال اي حاجة اللي بدات فكرة شرح الAgile بالعربي علي الblog بتاعها www.shokrof.com

What's hot (19)

Scrum Bangalore 18th Meetup - October 15, 2016 - Elasticity of Kanban - Saika...

DevOps: The Key to IT Performance

Agile foundation and agile myths

Agile 101

Scrum Bangalore 18th Meetup - October 15, 2016 - Agile Architecture - Deepak ...

Speed Dating for Project Management Software

Agile 101

cPrime FBI Agile Success

Richard Wilburn - Lean Truth

Agile Software Development proposal for UIW 3

Career Paths for IT Graduates

Agile 101 Agile Essentials In The Scrum Framework

Fundamentals of Agile

Ba ,agile and career prospects

Conducting Agile Retrospectives

Software Project Management - Introduction and fundamentals

Are you Agile enough?

Agile and DevOps Transformations in Large Organizations

Requirements hangout

Similar to Hints and Tips for a Business Analyst

WorkEngine Overview

EPM Live

EPM Live is a global leader in enterprise project, portfolio, and work management solutions. It offers pre-built solutions on the Microsoft platform to provide project visibility, resource management, scheduling, collaboration, and more. EPM Live has over 5,000 customers in 35+ countries and has received recognition from Microsoft, PMI, and others. It provides a full suite of solutions for strategic portfolio management, project management, agile management, and work management through its WorkEngine product.

The Digital Creative Process

storybridge

This is a summary of the process to follow when creating and building websites and other such online media. It's a project process overview for thos in need of such a structure to help run their projects and for clients to get a better idea of how the whole process works. There ar of course other ways of running your projects but this is a good tried and tested stage by stage way of doing it. I've included responsibilities and example outputs as well as key things to do and watch out for each stage.

Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)

projectingIT

This webinar discussed how PRINCE2 and Agile methods can be combined for project management and delivery. It provided overviews of the PRINCE2 framework and Agile methodology, explaining why they should be brought together. The presentation described how PRINCE2 can provide governance and control at the macro level while Agile enables micro-level controls during solution development. It also outlined APMG qualifications in Agile Project Management and how attending organization projectingIT provides training in PRINCE2 and Agile. The webinar concluded with contact details for further information.

Project design and management

Andrew Zolnai

The document discusses project design and management concepts. It covers topics such as project definition, quality assurance, proposals, project start, and project implementation. Key aspects include developing initial project concepts, proposal development, assembling proposals, project initiation, planning, execution, monitoring and control, and closeout. Project roles and phases are also outlined.

Endava Career Days Jan 2012 Analysis and Architecture in Endava

Florin Cardasim

This document discusses software quality and architecture practices at Endava. It introduces the Analysis & Architecture discipline, which focuses on business analysis, system analysis, and architecture. Business analysts elicit and document requirements, while system analysts focus on design and technical specifications. Architects own the architecture including tools, technologies, and strategic decisions. The document discusses how Sonar is used to measure code quality across factors like coding standards, comments, duplication, complexity, tests, and dependencies. A toxicity matrix measures architectural quality by assessing dependencies between code components.

Endava Career Days Jan 2012 - Analysis And Architecture in Endava - How do w...

Endava

This document discusses software quality and architecture practices at Endava. It introduces the Analysis & Architecture discipline, which focuses on business analysis, system analysis, and architecture. Business analysts elicit and document requirements, while system analysts focus on design and specifications. Architects own the architecture including tools, technologies, and strategic decisions. The document discusses how Sonar is used to measure code quality across various axes like coding standards, comments, duplication, complexity, and unit testing. Architecture diagrams and matrices are presented as tools to enforce rules and visualize dependencies. Finally, a toxicity chart is introduced to classify software quality issues.

NG BB 05 Roles and Responsibilities

Leanleaders.org

The document discusses roles and responsibilities in continuous process improvement (CPI). It describes the CPI deployment director as owning the deployment plan and communication plan. Project sponsors are responsible for the project charter and removing barriers. Process owners implement process changes. Black belts and green belts lead CPI projects under a master black belt. A DACI chart defines roles as drivers, approvers, contributors, and informers. CPI uses tollgates to approve project definitions, measures, analyses, improvements and controls.

Agile From the Top Down: Executives & Leadership Living Agile by Jon Stahl

LeanDog

The document summarizes a presentation by Jon R. Stahl on getting executive leadership and organizations to practice agile principles from the top down. It discusses how most agile movements are not sustainable because they fail to change culture and establish a process. It advocates that leadership must live the values of agility, seek to understand their unique culture, and be transparent. It also provides examples of information radiators that can help visualize work, values, projects and assets to establish transparency and shared understanding.

E-Business Suite 1 _ Dean Herback _ E-Business Suite Projects, vision, roadma...

InSync2011

The document outlines Oracle's E-Business Projects vision and roadmap. It discusses Oracle's leadership in project portfolio management and how its E-Business Suite provides visibility and control for project-driven organizations across various industries. Recent enhancements to Oracle Projects include improved integration with third-party tools, enhanced reporting and analytics, and new resource management capabilities. The roadmap focuses on continued innovation to support the full project lifecycle.

Agile software development for startups

Hemant Elhence

Business analysis and project changes

IIBA Romania Chapter

The document discusses business analysis and related topics: - It defines business analysis as the set of tasks used to work with stakeholders to understand an organization's structure, policies, and operations in order to recommend solutions that help the organization achieve its goals. - Key aspects of business analysis include standardization through frameworks like BABOK, as well as adaptability to different organizational contexts and changes. - Business analysis plays a role throughout a project life cycle from planning and requirements gathering to solution design, development, and post-project operations and maintenance.

Pir

euwebtc01

The document provides guidance on conducting post-implementation reviews (PIRs) of government projects. It defines a PIR as an evaluation of whether a project achieved its objectives and a review of project management performance to capture lessons learned. PIRs help departments improve service delivery, ensure funds are well spent, and demonstrate accountability. The guidelines recommend selecting important, high-cost, or pilot projects for review. A PIR can be conducted after project closure or periodically for long projects. It involves defining objectives, assessing outcomes and management, collecting and analysing data, and identifying lessons. Conducting PIRs helps optimize resource use and project delivery.

Pir

euweben01

The document provides guidance on conducting Post Implementation Reviews (PIRs) of government projects in Hong Kong. It aims to help evaluate whether projects achieved their objectives and identify lessons learned to improve future project delivery. The guidance outlines a four-stage model for conducting PIRs that involves defining objectives and scope, determining the review methodology, collecting and analyzing data, and identifying lessons learned and reporting. PIRs help ensure public money is well spent, services are delivered effectively, and accountability is demonstrated.

Pir

euwebsc01

$C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010$ $C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010$

C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010

BPM Link

Maria Horrigan discusses the importance of understanding users in business process design and improvement. She emphasizes that project success relies on meeting user needs rather than just focusing on the process or technology. Horrigan describes using personas and "want maps" to capture user behaviors, preferences, and needs in an agile project. She predicts that the focus on users and adoption of agile methods will continue to increase in 2010.

Design in Practice (V1)

Kmanthei

Linda Luu presented on Agile Design at Agile East 2011. Some key points: 1) Traditional design places user feedback late in the process, while Agile design engages users early and often with prototyping for rapid feedback. 2) Agile design uses a framework of short iterative cycles of concept creation, design, testing, and building to deliver concepts. 3) Benefits include the ability to respond to change, continuous feedback, avoiding rework, and implementing a validated design.

Key Considerations for a Successful Hyperion Planning Implementation

Alithya

The document provides an overview and recommendations for a successful Hyperion Planning implementation. It discusses key project phases, recommended build techniques including application definition, dimensionality, master data integration, building the planning model, and form and calculation development. It also covers tips for planning design including delineating plan types, defining dimensionality, integrating master data from various sources, and best practices for building forms to ensure performance.

Are projects agile?

Andy Longshaw

Agile Software Development - making programming fun again

calenlegaspi

This document discusses agile software development practices. It covers topics like iterative development, user stories, test-driven development, one team approach, self-managed teams, and sustainable pace. Some key benefits of agile include early detection of mistakes, improved communication between customers and developers, and ability to adapt to changing requirements. Specific practices covered in more depth include iterative development with working software at each iteration, writing user stories from the perspective of users' goals, and test-driven development where tests are written before code to ensure quality.

Secrets to Project Management for the Creative Studio

Daniel Schutzsmith

This document provides an overview of project management for creative studios. It discusses the key phases of a project including discovery, design, development, and deployment. It also covers topics like managing clients and teams, staying organized, and dealing with change orders. The goal is to help creative professionals and students understand project management principles and best practices to successfully plan and complete projects on time and on budget.

Similar to Hints and Tips for a Business Analyst (20)

WorkEngine Overview

The Digital Creative Process

Webinar on PRINCE2 + Agile - by Ashish Dhoke (projectingIT)

Project design and management

Endava Career Days Jan 2012 Analysis and Architecture in Endava

Endava Career Days Jan 2012 - Analysis And Architecture in Endava - How do w...

NG BB 05 Roles and Responsibilities

Agile From the Top Down: Executives & Leadership Living Agile by Jon Stahl

E-Business Suite 1 _ Dean Herback _ E-Business Suite Projects, vision, roadma...

Agile software development for startups

Business analysis and project changes

Pir

$C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010$ $C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010$

C:\Ihc\Bp Mlink\Presentations\Bpm Link Canberra Feb 2010

Design in Practice (V1)

Key Considerations for a Successful Hyperion Planning Implementation

Are projects agile?

Agile Software Development - making programming fun again

Secrets to Project Management for the Creative Studio

More from IndigoCube

IndigoCube Digital training catalogue

Hints and Tips for a Business Analyst

More Related Content

What's hot

What's hot (19)

Similar to Hints and Tips for a Business Analyst

Similar to Hints and Tips for a Business Analyst (20)

More from IndigoCube

More from IndigoCube (17)

Recently uploaded

Recently uploaded (20)

Hints and Tips for a Business Analyst