7 Misconceptions of Enterprise Agile

7 Misconceptions of Enterprise Agile

“Pure” agile approaches don’t simply “plug” into the enterprise environment as easily as they do in smaller organizations and centrally located teams. This webinar explores common misconceptions of agile specifically in the enterprise, so you can understand the real ways in which enterprise agile can help make Business Analysis and requirements authoring easier and more effective leading to better project outcomes with far less rework along the way.

  1. Enterprise Agile will free you from having to do requirements
  2. You can define business needs with well-defined user stories
  3. User stories alone are adequate to support compliance and audit
  4. Enterprise Agile will drastically change the way you do business
  5. Business Analysis is an organizational drag
  6. Business applications can be understood from code and tests alone
  7. Enterprise Agile will free you from having to use requirements software

via Webinars > 7 Misconceptions of Enterprise Agile: What You Need To Know

3 Ways Business Analysts Enable Agile Success (IAG)

http://agilemanifesto.org/

agile misconceptions

  • agile means no documentation (–> documentation that provides value, as and when needed)
  • agile means no planning (–> more short term planning, less long term)
  • agile doesn’t need business analysts (–> 6  tips for successful agile analysts)
    1. don’t act as product owner – unless you are
    2. 80/20
    3. plan iteratively
    4. be flexible
    5. the product backlog is not a requirements specification
    6. facilitate rather than dictate

via http://www.iag.biz/resources/webinars/webcast-3-ways-business-analysts-enable-agile-success.html

Scaled Agile Framework

In Agile Software Requirements ([1],Chapter 21), we described such a kanban system as depicted in Figure 1.

This portfolio kanban system describes four queues that an Epic passes through on the way to implementation (or rejection):

  • Funnel–the capture state, where all new business ideas are welcome
  • Backlog–where preliminary estimates of opportunity, effort and cost of delay are established
  • Analysis–where the more thorough work is done to establish viability, measurable benefit, development and deployment impact, and potential availability of resources. Development of a lightweight business case for consideration.
  • Implementation– where epics that are selected are allocated to the Release Trains that have with the resources and skills necessary for implementation.

via Business Epic Kanban « Scaled Agile Framework.

Mastering Scrum – The Common Pitfalls and How to Overcome Them

Explains the process and covers the “scrumdamentals”, using Microsoft imagery.

JJ159336.4B696E6D6383D8538BA5A7684F13BD42(en-us,PandP.10).png

This video is great for anyone who is looking to implement Scrum into their organization or team. They cover:

  • The history of Scrum and Agile
  • Product Owners (“budgetery power”, availability) and Scrum Masters
  • The various events and artefacts of Scrum and the roles of the team members

The challenges that Gerard and SSW have found during their years of experience and how they overcame them

via Mastering Scrum – The Common Pitfalls and How to Overcome Them | SSW TV.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s