Deliver Early - There Is No Excuse!
Jesper Boeg discusses why it is important to deliver software early, why it is difficult to do so, along with tools/tips/practices: shared vision, story maps, coaching, and others.
Jesper Boeg discusses why it is important to deliver software early, why it is difficult to do so, along with tools/tips/practices: shared vision, story maps, coaching, and others.
There have been numerous attempts over the years to determine the best way to measure the effectiveness of an Agile adoption. Some recent articles have reignited the debate around the most useful metrics.
During his talk at DevOps Days in Gothenburg Mitchell Hashimoto, co-author of Vagrant and system admin at Kiip, proposed an experience-based roadmap for moving organizations from a traditional black box ops culture to an (ideal) white box culture where developers are free to change the production environment.
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?
Article “Purpose Case Management” describes a Case Management method that overarches BPM and Adaptive Case Management. Author reviews several modern movements such as Unstructured BPM, Social BPM, Dynamic BPM, and ACM. The article concludes with a generic method that allows switching between BPM and ACM depending on which one of them is more efficient in an execution context at certain moment.

In this IEEE article, authors Neil Harrison and Paris Avgeriou discuss a pattern-based architecture review (PBAR) process to help with system-wide quality attributes. They also discuss how PBAR approach helps with agile practices like frequent releases, changes for user needs, and lightweight documentation. They illustrate the benefits of PBAR process with a real-world project.

In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.
Barry emphasizes the need to continue thinking critically about the processes and practices we embrace, accounting for the context in which they exist, and the importance of reflection and refinement at both the organizational and personal levels.
Leisa Reichelt proposes a detailed process for delivering a great UX starting from the original vision of the product, to business strategy, to customer experience strategy and tactical execution.
Nat Pryce presents the reengineering effort made to transform a legacy system through incremental improvement, the development process implemented, the results and some takeaway lessons learned.

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches. Jesper also discusses the benefits of integrating elements of Kanaban into existing Scrum teams and what can be achieved from the team seeing the entire value chain and owning the whole process.