Event Cover Image
Event Image
🚀 Join us this August for the first-ever SDLC Simulation by the IIBA Tampa Bay Chapter in Florida USA, designed for emerging professionals, students, professionals, and career changers who want to break into tech and business analysis roles with real experience. 👥 Step into roles like business analysts, product managers, project managers, developers, and more. 💡 Collaborate in real-time using tools like Mural, Miro, Visio, and more. Learn by doing. Grow by leading. 🎓 Certificates. 🏆 Awards. 🤝 Community. 📲 Want to be the first to know key details? Follow us, IIBA Tampa Bay Chapter in Florida USA and stay tuned.
This event is designed for educational purposes only and not a paid position.
 
Learning objectives - Participants who attend the 11 week Tampa Bay IIBA SDLC Simulation will learn:
1. Identify and describe key activities and deliverables in each SDLC phase
From requirements elicitation to analysis, design, development, testing, and deployment, participants will explore real-world artifacts, models, and workflows.
  • Example: Create a phase-by-phase roadmap with role-based contributions
2. Translate business problems into minimum viable products (MVPs)
Participants will apply Agile principles to scope MVPs within realistic time, resource, and technical constraints, articulating acceptance criteria and delivery value.
  • Example: Break down a business scenario into user stories and deliverables
3. Collaborate effectively with cross-functional SDLC roles
Through interactive role-play and peer exercises, participants will build empathy and shared language with PMs, BAs, Devs, Testers, and Product Owners, identifying core goals for each.
  • Example: Conduct mock standups or model Kanban flows based on team perspectives
4. Apply Kanban principles and function as a self-directed team member
Participants will use visual task boards (e.g., Trello, Azure DevOps) to manage WIP, prioritize tasks, and maintain accountability within the team structure.
  • Example: Track story grooming and identify blockers using swimlanes and tags