Scrum is a self-managing techniques that help software to be packaged iteration over iteration over a set of business critical feature. The iteration approach suites well to implement and release bunch of feature ready to be launched to the market. In mondora we focus on a Perpetual ß tool that helps us in finding and maintains the right path for the goal.
In mondora we're working with Scrum for several years, and we find it useful to log and organize on a sheet: the process, the actors and the things produced iteration over iteration. This helps me and all parties during the development how us in mondora are approaching industrial software development: in a really open way.
The archetypes we produce are refined iteration over iteration; for example, while discussing the Sprint at the Sprint Planning meeting we try to figure out how the next feature implementation will fit on an architecture and we will produce some architectural document.
A set of feature is committed for a sprint, and the industrial approach stages directly the alfa version during development time. Because we're working on features, we're focusing on statement that creates value and at the end of a Sprint we're ready to launch them as a Beta feature.
This happens iteration over iteration.
This only because Agile focuses on the idea that everything in a sprint is "something potentially shippable." We then stage the next sprint and fix all the bugs in the prior consolidating those beta services as stable services and releasing new beta services.
This happens Iteration over iteration.
Every time, every day we're looking at our Perpetual ß scrum sheet tool to know how, what e who is involved in the process and which will be the delivery. Of course, our tool is in ß too, and is growing day by day.
The archetypes we produce are refined iteration over iteration; for example, while discussing the Sprint at the Sprint Planning meeting we try to figure out how the next feature implementation will fit on an architecture and we will produce some architectural document.
A set of feature is committed for a sprint, and the industrial approach stages directly the alfa version during development time. Because we're working on features, we're focusing on statement that creates value and at the end of a Sprint we're ready to launch them as a Beta feature.
This happens iteration over iteration.
This only because Agile focuses on the idea that everything in a sprint is "something potentially shippable." We then stage the next sprint and fix all the bugs in the prior consolidating those beta services as stable services and releasing new beta services.
This happens Iteration over iteration.
Every time, every day we're looking at our Perpetual ß scrum sheet tool to know how, what e who is involved in the process and which will be the delivery. Of course, our tool is in ß too, and is growing day by day.
Tool is available to download here: mondora-perpetual-beta-scrum
0 commenti:
Post a Comment