Business analyst in agile projects

2,217 views

Published on

Business analyst in agile projects

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,217
On SlideShare
0
From Embeds
0
Number of Embeds
31
Actions
Shares
0
Downloads
94
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Business analyst in agile projects

  1. 1. Business Analyst in Agile Projects<br />Agile Management Solutions<br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  2. 2. BA Traditional Activities<br />Scope the System-Creation with stakeholders of a “business vision” of the project. <br />Initial Requirements-Translating high level discussions with stakeholders into documents. <br />Document the Business Needs- Create a document that the business can read. <br />Document the Business Needs-Create a document that was a iterative process from the developers (questions, answers) that the business and developers can read. <br />Technical Translation-Explain technical complexities to project stakeholders, such as architectural , infrastructure, code selection. <br />Explain to Developers-Why is this project being created and why does the business think it should be created in this fashion. <br />Explain to Business-What developers are doing and Why are they doing it this way.<br />Schedules-Estimates and basis of the timeline<br />Model Documentation-Business details documented as per domain and project. <br />Communications-Between the business and development teams.<br />Validation and Testing-Walk through, demos, documenting results.<br />Stakeholder Representation-Liaison between teams for the project life-cycle.<br />Politian -Liaison for entire organization and all teams involved in the project.<br />   <br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  3. 3. Common Project Problems<br />Lack of Skills-Wrong people put into the role and they will never have the opportunity to gain the skills needed to thrive in the BA role. <br />Too Much Influence-Some BA’s will try to influence the project, not the stakeholders and might play politics. <br />Out of Date BA Skills-Trained on Cobol projects but working on object-oriented web projects. <br />No Understanding of the Technology-They need at least minimal understanding of the technology that the project is going to be developed on.<br />Communication Barrier-BA’s that act as a barrier instead of a conduit for the project.<br />Over Analyzing-Focusing on their specialties and what they are comfortable with , not on all the tasks involved in the project. EX:Time spent on documentation and little spent on modeling.<br />Communication-Poor feedback between team members for the length of the project life-cycle.<br />Anti-Team Creation-Using only one conduit to go through does not create well running teams.<br />Limiting Skill Sets-If team members only go though the BA then developers and other teams members never get the chance to improve their communications skills by dealing with the business. <br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  4. 4. Re-Thinking the BA Role Agile Style<br />Co-located and Team Generalists<br />Team members working side by side and team members that have one or more technical specialties and are striving to gain new skills. <br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  5. 5. Agile Style Success<br />Agile Estimation-Includes prioritization of requirements.<br />Agile Communications-Face-to-face discussion with team members.<br />Project Stakeholders-Team members like to work closely with business.<br />Iterative Analysis-Estimating and Design efforts placed on a team as a whole.<br />Incremental Analysis-No need to build the systems all at once.<br />Exploration Analysis- Understand the need for your system then communicate efficiently with the entire team. <br />Agile Documentation-Just good enough not perfect just good enough.<br />Disciplined Change Management-Each integration implement the highest proity items.<br />Modeling-Use simple tools (flip charts, boards) to make it easier for stakeholders to participate.<br />Terminology-Use universal terminology through out the entire life-cycle.<br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  6. 6. Conclusion<br />Agile means self-organization, test driven development, collaboration teams, face to face communications and teams based on IT generalists. <br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />
  7. 7. Paul Gravinahas been working in the Information Technology arena for the past 15 years. He has worked in a variety of roles related to technology such as Quality Assurance, Business Analyst and Project Management. He has been certified as a Six Sigma Green Belt and is the owner of Agile Management Solutions an IT contracting firm. Paul also contributes to the blog Agile Management Solutions <br />© 2010 Agile Management Solutions. (AMS LLC) All rights reserved. <br />

×