We gather the requirements of stakeholders on both the business and IT side. We analyze the current development and QA functions and identify points for improvement. Together with your in-house team, we create a detailed, actionable project plan focusing on low-hanging fruit-type quick enhancements and programs for complex, systematic changes.
We help create a common vision between business users and IT development teams about the agile way of working together. We believe in a human-focused, practical approach in introducing lean principles, agile values and the scrum framework tailored to your current operation. The result is a new mindset focusing on business value delivery, leading to a better performing (and ever-evolving) development process, delivering digital products faster.
We train and mentor product owners, scrum masters, project managers, business analysts, solution architects and development team leads. We help select a standardized kit of best-of-breed tools and techniques. We also put emphasis on communication and management practices and leadership skills that help to maximize team performance.
As specialists of coding automation, we review the level of automation in your development, testing and deployment operations, and suggest up-to-date technology solutions. We implement process mapping, documentation best practices and risk management planning.
Faster feature development
Increased predictability of software delivery
Better software quality
Cost-effective development and testing
“Paranoia is the secret to longevity” (Vavyan Fable, The Bone Flute) is not only true in the world of crime fiction (Fable’s book follows a modern cat burglar working online, targeting everyone from individuals to banks and multinational companies) but also true to life.
Over the recent years, the attention placed on modeling and modeling devices has heavily declined. While there could be multiple reasons for this*, the fact is that the robustness of the standard modeling language (UML) and modeling tools are not helping the situation. In a number of projects however, it would be reasonable to use smaller, more domain-specific languages but they often require setting aside the convenient features typical to today’s development environments. Or do they?