Lightning talk: Business analyst role as agile villain in legacy projects
•
0 likes•154 views
How could a business analyst perform his role using agile as a framework in a big legacy project?. Under this context, the business analyst and the project itself are victims of the situation. Presentado por Emilio Contreras en SG Virtual 2020
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Lightning talk: Business analyst role as agile villain in legacy projects
Similar to Lightning talk: Business analyst role as agile villain in legacy projects (20)
More from Software Guru
More from Software Guru (20)
Recently uploaded
Recently uploaded (20)
Lightning talk: Business analyst role as agile villain in legacy projects
- 1. Business Analyst Role as Agile Villain in Legacy Projects J. Emilio Contreras Llano Business Analyst and Product Owner @ Unidos compartiendo y aprendiendo #SGVirtual
- 2. What are we going to talk about? Business Analyst Role Legacy Projects Agile Methodology Business Analyst @ Agile Legacy Project + BA Why am I a Villian?
- 3. Business Analyst Role • Bridge between Customer and Development Team • Right hand of the Project Manager. • Manages many tools and techniques. Prepare 1 1
- 4. Legacy Projects Old but meaningfull Projects Mainframe, COBOL, unsupported Windows, early 2000’s Oracle versions, old frameworks, etc… Functional Technologies Companies used to implement ITIL or CMMI best practices. Originaly Development under other methodology
- 5. Agile Methodologies Product Owner, Scrum Master, Team Manager, Team members. Well defined Team Release functional pieces of the Project. Small MVPs Workload divided by sprints or iterations. Iterative Business Analyst, Scrum Master [Iteration Manager], Team Manager , Team members. Business Analyst @ Agile 2 3
- 6. Legacy Projects With An Agile Business Analyst During these years, companies give less priority. Reduced budget As these are old Project, things changed during years. Change on the Methodology Primary source of functional requirements is gone. Stackeholders, SMEs and more not in the process anymore An Agile Team does not need a project manager, but sometimes they have it. Project Manager Resources has been changing during the lifetime of the Project. New Solution Team
- 7. Why Am I A Villain? • Not a role designed with the project. • Do not Follow the Agile Ceremonies. • Your goals goes beyond Agile practices. • The past is not always something bad. • Help yourself with other methodologies’ tools and practices. Then… 4
- 8. Thanks! J. Emilio Contreras Llano Business Analyst and Product Owner @ Unidos compartiendo y aprendiendo #SGVirtual /jemilio928/ @jemilio928
- 9. Bibliography Carkenord, B. A. (2016). PMI-PBA Exam Prep. In B. A. Carkenord, PMI- PBA Exam Prep (pp. 23 - 177). Minnetonka: RMC Publications, Inc 1 2 Raza, M. (2918, May 13). Agile Roles and Responsabilities. Retrieved from bmc: https://www.bmc.com/blogs/agile-roles-responsibilities/ West, D. (2020). Scrum roles and the truth about job titles in scrum. Obtenido de Atlassian Agile Coach: https://www.atlassian.com/agile/scrum/roles 3 2 Aston, B. (2019, April 23). 9 Ejemplos De Metodología De Un Proyecto, Simplificados. Retrieved from The Digital Project Manager: https://thedigitalprojectmanager.com/es/metodologias-gestion- proyectos-simplificadas/
Editor's Notes
- We Will discuss the Business Analyst and Agile topics very few but at the end I can provide some documentation if someone is interested.
- Needs to be a technical person and understand the customer needs, the business side, the main goal to archive Requires to understand perfectly what the client or business needs so he can créate the stories, epics and requirements for a better understanding of the dev team He needs to be very clever and documented on the tools and techniches he uses for his role
- Old is a relative term Teams, communities or companies delivering that technilogy Adquiring need resources, status reporting and keep Project scheduling ongoing. Finish speaking about the methodology to link it to Agile, mentioning that these Projects used to have a Project manager…
- Agile Teams does not need a Project manager, surely the team needs a role that performs the resoulse management and perform the análisis of the Product Owner or business requirements, here comes the Business Analyst in this team, Business Analyst is a role comming with new projects and not with waterfall Agile divided theit MVPs by Iterations, this difined by the Team but task of the BA to Finishes mentioning that the business Analyst needs to adapt waterfall to what agile is
- Business Analyst in a legacy Project almost implice that the BA is new in the team with LOT of things to learn and here is where gets interesting… he faces a big barrier that includes
- Projects are enormous, so hard to understand and agile takes much time to implement and change the paradigm [peredain]. As Older methodologies used to have a lot of documentation. Design thinking, XP, CMMI, SCRUM, Kanban, PRINCE The BA is an agile villain because he needs help from other methodologies, tools and techniques apart from agile to perform his role, Or to ignore completely agile and adjust your job into a mix of different ones from all methodologies, even create you owns, this is something I’ve seen many many times with some of my partners.