Organizations using the Scaled Agile Framework (SAFe) might want to integrate a business analyst (BA). This proves rather difficult, since SAFe has not included this role in its framework. This leaves many organizations questioning how a BA could be integrated into the process. They opt to have a BA flesh out what needs to be developed. This sometimes leads to conflict with the Scrum teams or a requirements engineer of a team.„How to integrate business analysts into SAFe“ weiterlesen
In a discussion in the IIBA LinkedIn group, someone asked ‚Are any of you using UML, and how is working out for you?‘ The answer is like always: ‚it depends‘. It depends on the situation and what others expect.
By now, most organizations should have understood that they have to become more agile in order to stay in business. Like any new trend, people need practice to use it correctly. Some organizations have taken shortcuts and bent the rules of Agile and Scrum, and „forgot“ to think before they started to implement. A software development will seldom be successful without some form of thinking, specification, and documentation. The question is „how much thinking is actually useful?“
Kollegen berichten mir häufig, dass sie in ihrer Arbeit untergehen, anstelle in ihr aufzugehen. Sie erhalten kontinuierlich neue Aufgaben, die sie beginnen müssen, ohne die laufenden beenden zu können. Der stetig wachsende Stapel an unvollendeten Aufgaben erzeugt bei uns Menschen Stress und macht uns auf Dauer unzufrieden, denn wir wollen Aufgaben bestmöglich erledigen und diese abhaken dürfen.