Do you find that user stories grow and multiply until you can’t fit them in your Scrum sprints? Are you struggling to see the big picture? Are you lost in user story hell? This presentation examines the OOPSI (Outcome, Output, Process, Scenarios, Inputs) technique and demonstrates how it accelerates delivery by ensuring that you are always working on the right thing and can see the bigger picture.
The Product Owner is a key component of Scrum teams as the role a major influence on software development projects. It is however not always possible for the Agile team to get access to a full-time qualified Product Owner. This is why Marcelo Leonetti discusses in this article some situations where a Product Owner proxy could help Scrum teams solve some problems.
So now that everyone and their dog is Agile, what has really changed? Are we really „delivering more value in less time“ as many agile approaches promise. What do we even mean by value? How do we know when we have delivered value? When we are “done” according to our “Definition of Done”, or when we can validate that a feature is being used by our customers?
Agilia Budapest is a three-day conference focused on Agile software development. The theme of this edition is the role of product owner and product management in Agile: creating vision, designing product, managing teams, role of Product Owner, engagement of customers and users, creativity and management of innovations. Use cases.
Projects have been the main working mode of software development activities since the beginning of computers. According to Allan Kelly, it is however not the best mode to develop software. He fosters the #noproject movement to fight project myopia that he defines as the “belief that the project model is the only way of managing business change and development.”
As the Agile Manifesto stated that it prefers “working software over comprehensive documentation”, some early Agile adopters jumped to the conclusion that documentation was useless. Thus Scrum software developers should only concentrate in creating working software with code that was the most easier to understand.
Agile and Scrum team formation is a natural human response to certain conditions. Once they exist, the formation process begins. This session looks at those conditions, and then looks at what other conditions need to be reached to progress through the different stages defined by Bruce Tuckman: Forming, Storming, Norming, and Performing.
Scrum Expert Copyright © 2009-2024 Martinig & Associates