top of page

Team 01

Dedication. Expertise. Passion.

Our team represents six countries, five time zones, and a wide range of levels of experience. 

When we formed, we were a group of strangers - now we are a working team!

Team Mentor

Screenshot 2025-10-11 142619.png
Misti Chancellor

Oklahoma City, OK, USA

 

20+ years of BA experience, 5+ years of (manual) QA experience, 10+ years of Agile methodology experience, including teaching an Into to Agile course to over 100 individuals, as well as a short stint as an interim Project Manager for a large project.

 

If I don't know the answer, I can probably find someone who can get it for us.

Project Manager & Product Owner

Screenshot 2025-10-11 142334.png
Fatima Ahmed, BSc/MBA 

​Lagos, Nigeria

​

Business Support Specialist with 6+ years combined experience in Project management, business analysis, and customer service.

 

Over the past 3 years, I’ve led and supported projects that bridge innovative tech solutions, and user needs.

​

Through this program, I’m refining my skills to deliver even greater value and smart results.

Business Analyst

Screenshot 2025-10-11 142258.png
Azuka Azodeh 

Lagos, Nigeria

 

Business Analyst with 4+ years of experience in business analysis, hospitality, and SME consulting. Two years in the automotive sector, I’ve managed project deliverables, facilitated cross-functional meetings, and provided functional support in agile environments. Focused on process improvement and aligning business needs with technology, I’m leveraging this program to refine my analytical and product management skills for business value propositions and visibility for global opportunities.

​

https://www.linkedin.com/in/azuka-azodeh

Quality Assurance

Screenshot 2025-10-11 142402.png
Felix Ugbesia 

Nottinghamshire, UK

 

With several years of experience in banking and hospitality consulting, I specialize in solving complex business challenges by aligning digital solutions with strategic goals.

 

My approach blends stakeholder collaboration, data-driven decision-making, and practical insight to drive innovation, efficiency, and measurable value

Quality Assurance

Screenshot 2025-10-11 143811.png
Michael Moser, CBAP

Houston, TX, USA

 

IT Business Analyst of 8 years with 2 years as a FE Developer, I've spent most of my career in the IT Consultancy space.

 

Primarily working within Agile projects, I'm coming off a heavier QA stint but have intersected with most layers of the SDLC at some point.

Developer

Screenshot 2025-10-11 142502.png
Will Powers

Cincinnati, OH, USA

​

Operations Analyst of 3 years with 1 year of sales support experience and 3 years of call center experience. Within my currently role I work on a developing product which has given me exposure to most layers of SDLC to some degree.

​

In addition I have worked as a developer on quite a few side projects for various organizations.

User Interface & User Experience

Screenshot 2025-10-11 142540.png
Emmanuel Adepoju

University of Ibadan, Oyo, Nigeria

​

Multidisciplinary designer focused on creating seamless, memorable digital experiences. I’ve worked on mobile apps, websites, dashboards, and brand systems—bringing together usability, aesthetics, and strategy.

 

Skilled in Figma, design systems, and visual storytelling, I thrive at the intersection of product and brand.

Team Observer

Screenshot 2025-10-11 142708.png
Ifeoluwa Ajidahun, MBCS

​United Kingdom

​

Business Analyst with 3+ years’ experience in requirements gathering, business modelling, and digital transformation. Skilled in Agile delivery, stakeholder engagement.

 

I turn complex needs into clear requirements and help teams deliver user-focused solutions. Passionate about improvement and collaboration.

Problem Statement:
Sip Split: Project Reporting Dashboard

Splitting shared expenses after group outings or events often leads to confusion, awkwardness, and errors. Friends struggle to determine individual contributions, track payments, or calculate totals fairly.


Key pain points:

  • Lack of a simple, transparent system for splitting bills.
     

  • Manual calculations that lead to mistakes and tension among friends.
     

  • No existing lightweight web solution that combines simplicity, accessibility, and accuracy.
     

Solution Statement

We developed Sip Split, a simple and user-friendly web application that allows users to:

  • Input the number of participants and total bill amount manually.
     

  • Automatically split the bill equally and display a clear breakdown for each participant.

  • Deployed o google firebase
     

The solution was built to be scalable, accessible and supported by desktop and mobile

Screenshot 2025-10-11 145227.png

Kanban (Agile)

The Kanban Board is a visual project management tool used to track tasks and progress across workflow stages, typically To Do, In Progress, Under Review, and Done. it entails:

  • Clear task organization by status.

  • Assignment of ownership (PM, BA, QA, Dev, UI/UX).

  • Real-time progress tracking.

  • Visual control of bottlenecks and priorities.

  • ​

Relevance & Impact:
The Kanban board on Miro provided transparency amongst the team members. It allowed everyone to see what was being worked on, what was completed, and where blockers existed. This improved collaboration, accountability, and focus. It also made stand-up updates easier since progress was visibly trackable at a glance.

​

Miro Link: https://miro.com/app/board/uXjVJY_0SNE=/?share_link_id=331261449754

Project Deliverables - By the Project Manager

The Project Charter outlines the project purpose, scope, milestones, resources, risk and mitigation strategies adopted for the project amongst others before execution begins. It serves as the official “go-ahead” and defines why the project exists.

 

Relevance & Impact:
The charter set the foundation for the Sip Split project, aligning all team members on a shared vision and ensuring clarity on objectives and expectations. It helped stakeholders understand why the project mattered, what it aimed to achieve, and how success would be measured. Having this clarity from the start minimized confusion and guided decision-making throughout development of the project.

 

Lessons Learned:

Strengthened my ability to structure and initiate projects from the ground up.

Improved my documentation and communication skills by translating abstract goals into measurable deliverables.

Understood the importance of clarity and stakeholder buy-in during the initiation phase.

​

Miro Link: https://miro.com/app/board/uXjVJYa7LKk=/?share_link_id=439431480879


 

Screenshot 2025-10-11 140809.png
Project Charter

Project Deliverables - By the Project Manager

Timeline balance

The Timeline balance refers to the project schedule to ensure all tasks are distributed evenly, milestones are feasible and realistic, and tasks are manageable across the team. It’s allowed aligning deliverables with time constraints.

 

​

 

 

 

​

​

​

​​​​

Relevance & Impact:

Balancing the timeline helped maintain project momentum despite different time zones and schedules. It ensured key milestones, such as requirement elicitation, prototype design, test case drafting, and deployment, were achieved without burnout or delays. The ability to spot and remove blockers as needed was made possible because of a clear timeline balance.

What it entails:

  • Establishing clear milestones

  • Monitoring task progress against planned dates.

  • Adjusting priorities or dependencies as needed.

  • Ensuring no team role (e.g., QA or Dev) is overloaded.

Project Deliverables - By the Product Owner

Product Canvas

The Product Canvas is a strategic visualization tool that connects the business goals, user needs, and product features in one place. It bridges the gap between high-level vision and practical execution, helping teams align on what to build and why.

Screenshot 2025-10-11 145923.png

What it entails:

  • Vision and Goals: Defines the purpose of the Sip Split app — to make group bill splitting easy, fair, and transparent.

  • Target Users: Identifies users such as friends dining together, shared renters, or coworkers.

  • User Needs: Clarifies pain points like confusion over payment amounts or difficulty tracking who owes what.

  • Key Features: Highlights MVP features (bill entry, split calculation, summary view) and future enhancements (tip calculator, itemized split, and payment integrations).

  • Metrics for Success: Specifies what success looks like — e.g., smooth user experience, accurate calculations, and stakeholder satisfaction.

 

Relevance & Impact:

The Product Canvas kept the team’s focus anchored on value delivery rather than just technical outputs. It served as a blueprint for decision-making during design, backlog prioritization, and testing. By visualizing the user journey and linking it to business objectives, it ensured every feature built in the MVP directly supported user satisfaction and the project’s success criteria.

​

Miro Link: https://miro.com/app/board/uXjVJYa7LIQ=/?share_link_id=958710096010

Project Deliverables - By the Product Owner

Product/Decision Backlog

The Product Backlog is a dynamic, prioritized list of all features, enhancements, and fixes that was referred to meet the project’s objectives. It represents the single source of truth for what the team worked on and planning next.

What it entails:

  • User Stories: Clear, structured descriptions of user needs (e.g., “As a user, I want to enter the total bill and number of people so I can see how much each person owes.”).

  • Acceptance Criteria: Defines what must be true for a story to be considered “done.”

  • Prioritization: Organized from high-priority MVP tasks to lower-priority or future enhancements.

Screenshot 2025-10-11 141212.png

Project Deliverables - By the Business Analyst

PRD Structure & Details 

I created the PRD after week 1. We had  an internal team review on deliverables and expectations for the project.

The project deliverables were gradually compiled on the PRD and we reviewed it as a team atleast six (6) times.

Some of those deliverables are

Problem Statement, Objectives, Scope, User Stories, Acceptance Criteria and so on.

The importance of these were to ensure that when we were designing, we stayed within the scope.

​​

Lessons Learned
  • I had first hand experience in creating a PRD and it got a very good feedback.

  • I learned how important the PRD was to each member of the team as it ensured we stayed within scope.

  • I also learned about the importance of constant documentation and refinement in real time to ensure that my team and I collaborated efficiently with each other.

image.png

Project Deliverables - By the Business Analyst

Requirements Gathering

This is one of the most exciting areas for me on the project because it allowed my team and me to run amazing ideas on how we envision the product. We started with a traditional brainstorming session and ended up with round robin for more tailored requirements on the project.

​

What my focus here for the requirement gathering was we started filtering what our MVP would be based on the feedback of our developer, and we documented this too. 

Additional notes are technical notes and wireframe/mockups.

​

Find out more on our future requirements and MVP requirements gathered:

Miro Link - https://miro.com/app/board/uXjVJPR5lC0=/?share_link_id=694086968086

Screenshot 2025-10-13 121759.png
Screenshot 2025-10-11 152135.png

After requirements had been gathered on what our expectations were for the webpage, we also had a review of our problem statement, scope objectives, etc., for our webpage, and it gave us some open ideas into the end-to-end handling process of the use case of SIP SPLIT.

​

Use Case Diagram

​Find out more - Miro Link: https://miro.com/app/board/uXjVJStFG60=/?focusWidget=3458764643627492837

​

Lessons Learned

No new knowledge was acquired here but I was able to showcase my knowledge on workflows.

Project Deliverables - By the Business Analyst

MVP (User Story & Acceptance Criteria)

After we had gathered our requirement as a team, we worked to get Epics, User Story and Acceptance Criteria. 

From the first table, you can see our MVP Epics, User Stories, and Acceptance Criteria.

Miro Link: https://miro.com/app/board/uXjVJPR5lC0=/?focusWidget=3458764643354038303

 
Lessons Learnt
  1. Gave clarity on how test cases were built in a clear and concise way.

  2. I built my User Story and Acceptance Criteria writing properly and it helped reshape my understanding. 

Screenshot 2025-10-11 152509.png

Project Deliverables - By the QA/Tester

Test Case Document: Its Benefit to the Team. The test case document functioned as a centralized reference artifact, significantly 

  1. It creates a shared ‘Source of Truth’ by translating a high-level requirement into a clear step-by-step validation process. This ensured the team had a clear understanding of what was in progress and what had been done. 

  2. These artifacts, covering some edge cases and error conditions, helped the team identify critical bugs that could have been missed, e.g., the assumption that the total amount was being rounded up to 2 decimal places.

  3. The test case artifact helped to enhance team-wide communication and collaboration by providing a central reference document that is significant for the DevOps team, comprising developers, BAs. PM, PO, UI/UX, and Tester. 

  4. It served as an accessible repository of test scenarios, expected outcomes against actual outcomes, and most importantly, feedback, which was looped back into the development of the Sip Split web application.  

  5. The Test Case Document helped the team to have a shared understanding by reducing miscommunication, which was sometimes the case, i.e., with the introduction of OCR as a COULD have feature rather than a MUST have feature.

  6. It provided the team with repeatable test steps for validating the functionality of the features as well as a clear and traceable path to the original product requirement.

Screenshot 2025-10-13 122004.png

Project Deliverables - By the QA/Tester

Benefits of Bug Log to the Team.
  1. This ensures all defect information, severity, date first mentioned, status, and comments are in one place, eliminating duplicity and confusion among the development team.

  2. The document helps the team prioritize the bugs that MUST or SHOULD, or COULD be released before launch. 

  3. The document helps the team to track the bug life cycle, i.e., from ‘new’ to Assigned’, ‘in progress’, ‘fixed’, to ‘verified’.

  4. This document benefits the team in such a way that it serves as a single source of truth for all bugs in the projects. New team members only have to read through to know where the team is with the issues arising from the bug. 

Screenshot 2025-10-11 152755.png
Will Powers, Developer

Project Deliverables - By the UI/UX Designer

Sip Split Application https://sip-split.web.app/

Live website below                                     Will Powers, Developer
Click below                                               Will Powers, Developer

Building the Sip Split Application 

Impact of the SDLC Experience Workshop

Screenshot 2025-10-11 142708.png

Team Observer

ifeoluwa Emmanuel Ajidahun

Ifeoluwa reports he is much more confident in his knowledge of SDLC after participating in the Workshop.  "The SDLC program has been a great learning experience, giving me a clear picture of how ideas progress into real, working solutions. It’s helped me understand how each role contributes to the bigger picture while improving teamwork, planning, and delivery. Watching the software take shape step by step has been especially rewarding."

​

"I appreciate the effort and structure the Tampa Bay IIBA Leadership has put into organising this program. It’s been a valuable learning experience that bridges theory and real-world practice. Thank you for creating an engaging and supportive environment for participants."

​

"Yes, I’d like to recognise Azuka (BA) for his clear and detailed requirements that guided the team effectively. Fatima (PO/PM) showed great leadership by keeping priorities clear and ensuring smooth coordination across roles. Micheal and Felix (QAs) maintained strong communication and thorough testing, helping the software pass all test stages successfully. William (Developer) brought the interface to life with great attention to user experience. Their combined effort and collaboration truly contributed to the project’s overall success."

Screenshot 2025-10-11 142402.png

Quality Assurance Analyst

Felix Okogie Ugbesia

Felix reports his confidence has increased as a result of participating as a Quality Assurance Analyst in the Workshop; "It takes patience, resilience, collaboration, adaptability, flexibility, and hard work to build software. That there is ONE and only ONE single 'Source of Truth' in SDLC, which is the USER stories derived from the high-level requirement, where all features MUST be traceable back to. "

​

"This workshop turned me from zero to near hero and ready for the transition that i had long desired."

Screenshot 2025-10-11 142334.png

Project Manager and Product Owner

Fatima Ahmed

"I gained a lot from this program. Firstly, it opened my eyes to the role of a product owner, and now I want to explore it further. My project management skills and experience have been greatly enhanced, and now I feel more confident in taking on the role of an IT project manager. I also learned to use Miro and Balsamiq for the first time."

​

And for the future?  "I will be better positioned to lead a diverse and multi functional team and also provide a smart result. "

​

In recognizing mentors or team mates, "Yes, everyone did a great job but i want to specially recognize Thea, the technical team, (Esther and Cossi), the following Team 1 members for their great efforts the Dev, Williams, the BA, Azuka, and QA2, Michael. Their consistency and diligence to their roles ensured a team success.  Just a big THANK YOU to Thea and the entire IIBA Tampa Bay Chapter for this great opportunity."

Screenshot 2025-10-11 142258.png

Business Analyst

Azuka Azodeh

"I gained a lot of hands on experience, like use case diagrams, and learning how to build by PRD. 
Additional skills which were improved on were working and building of test cases.
Collaboration with all team memebers and at the right time
I practiced how to give constructive feedback."​​

​

And for the future? "1. I would first of all take a deep breath, and remind myself I can handle what comes my way.
Read my problem statement if it is ready and ask enough questions before I start to build.
2. Another thing I would do is always bring my team to ensure we are in thesame page and working within the scope of the project."

​

In recognizing mentors or team mates, 

"1. Thea was amazing! a big shoutout to her for always being supportive throughout the project
2. Esther was also very supportive with our tech related issues 

now going into my team, team 1
1. Misti was very helpful and she helped break the ice with the MVP and that is when things became much clearer and easier.
2. Fatima our PO, was also very helpful and available to ensure we know what we were doing, how we were doing it and when we were doing it.
3. Will, was our amazing Dev bro and he was busy but made sure we were always on thesame page and gave us some great insights into the project.
4. Michael was our QA and he was also very supportive too, he stepped up and stepped in to ensure our team had structure alongside Fatima.
5. Felix was an amazing guy, he went across all team members and he tried to get his hands dirty to ensure we were moving.
6. Emmanuel was our amazing UI/UX creative, he ensure our product looed good, simple and easy to use.
7. Lastly, a big shoutout to myself, I stepped up as the BA for this project from the observers seat and ensured my team and I had all the support and resources we needed, I made myself available for meetings asked a lot of questions and shared ideas too.


Observer
1. Ifeoluwa was also a great support to our team and gave us support when we could."

Screenshot 2025-10-11 142502.png

Developer

Will Powers

I wanted to give a shoutout to everyone on the team for their effort and commitment. When we started this class, our work was quite fragmented, often ideas were confusing and at times conflicting, but the team powered though these hurdles and fully committed to their roles. Though the power of everyone’s combined efforts and multiple iterations, often requiring long nights and multiple huddle sessions we were able to design, test, and deploy a fully working prototype. Everyone on this team is incredibly talented and I would hire each and every one of them if I had the opportunity.

Screenshot 2025-10-11 142708.png

Observer

Ifeoluwa Ajidahun, MBCS

"Through observing the SDLC program, I gained practical insight into how cross-functional teams collaborate to deliver a software product from concept to completion. I developed a stronger understanding of project coordination, requirements management, and the use of Agile tools to maintain transparency and progress. The experience enhanced my analytical thinking and appreciation for effective communication and structured teamwork in achieving successful project outcomes.

​

Thank you for the opportunity to be a part of this program."

Awards and Recognition 

Do YOU have a story? Post it in BA Force Multiplier - I'm IN! 👉

  • LinkedIn

Need Assistance or Coaching? Contact Thea Soehren          👉

  • Website
  • create an icon for a calendar
  • LinkedIn

© 2024 by BA Force Multiplier. Web design by WebMox LLC

bottom of page