needs drive technology, technology enables needs This is about technology as a tool for solving needs not a tool for developing new needs. In here I will talk about how all technology is from core needs. I will also link to a chat about buinesses using techology development as a core buiness rathen then as an enabling aditive
- would be cool to talk about how companies can support need growth
- Businesses building IT as a core buisess function
- communication as a BA’s superpower
- The importance of buy in
- BA’s are guides as much as they are analyst
- Common language systems make communication a dream
Who, what, when, why and how as a framework for thing about stuff
- BA’s focus on the why not the how - dev and engineers focus on the how
Effective planning is a multiplier on output - not in the way you may think
- planning as a space for common laguage generation
- planning as a tool for buy-in
- planning as a space for low pressure negotiation
- Planning as a stake to be measure against
- Either change the activities to bring the project inline with the plan or change the documented plan so that it better fits with new information and situation needs. Don’t stray from the plan and end up in the jungle
- Spectrum between plan-driven and change-driven
- planning as an opperturnity to set the tone
Life cycles are a thing they happen
- mixing life cycles
- life cycles from a development perspective - waterfall iterative and agile
- Spectrum between plan-driven and change-driven
- A plan-driven approach assumes that most requirements can be determined up front and that the customer has a clear understanding of what it wants. In a situation like this, there is less of a need for iterations, prototyping, and frequent checkpoints. A change-driven approach, on the other hand, assumes that the product requirements will evolve throughout the development
- waterfall - plan driven
- agile - change driven
- plan driver and change driven as a perspective on BA
- stakeholder analysis
- is this a enterprise-wide underttaking where the companies future sucess is a stake - plan driven
- discorvy project? change driven
- stakeholder analysis
- process must be custom
- building custom processes as a BA
- pull from common library of process
- stakeholder analysis
- formal vs flexible as a framework for thinking about BA approaches and processes
- building custom processes as a BA
- you cannot fit the same tools to all projects - tree house vs skyscraper
Iterations, spiral frame work and IBM’s RUP
Agile and its many churches - People process and tools (the RAD system) - DSDM - SWAT People and where to find them (small didicated skilled with adv tools) - Scrum - SCALed - CASE (ICASE) - JIT 9 (just in time model storming)