Success Solutions
Modern market environment may bring many challenges in terms of project time management and customer satisfaction compliance. Our professional team of managers, solution architects, software engineers, DevOps and QA engineers will help you deliver on time and protect your investments.
APPLY HEREWhat is Agilego?
Agilego is add-on to Jira that provides the following functionality
- Resource allocation sheet for certain sprint
- Validates sprint plan consistency
- Illustrates sprint activities schedule on Gantt chart
- Tracks progress against baseline
Planning is an endless process. Nevertheless the planning efforts should be reasonable.
Our Project Management methodology AgilegoTM is based on industrial best practices and ISO/IEC 19761:2011
Why is it needed?
Currently Scrum is a very popular methodology for software development even for complex cross-functional and big scale projects. Lot of IT companies and their customers prefers Scrum as due to frequent and quick delivery of functionality, so it allows to ensure the product corresponds to expectations, react on changes promptly, etc. However Scrum has some cons, e.g. its recommendations are
- delivering incremental independent snippets of the product
- full time team member allocation on the project
- team is cross-functional and everyone has sufficient knowledge about QA, UX, integrations and all used technologies
There are discrepancies with all above listed theory and reality - dependencies between tasks, lack of resources with required expertise, etc. In result story points based capacity planning and burn-down charts are not effective as expected. How to fix this nonconformity? Some of possible options:
- dedicate more time to daily meetings or build enhanced reporting system in order to detect and fix issues with capacity, expertise bottlenecks or disregarded dependencies
- try to grow cross-functional developers with BA/QA/SME/etc expertise.
Both try to change reality to conform Scrum principles. Another possible option - combine Scrum and Waterfall practices. Such approach allows to ensure frequent deliveries and gives additional transparency from waterfall tools like resource sheet, Gantt chart, critical path, etc.
Why is it needed?
Agilego exports sprint, backlog, components and project employees data, transforms them and saves to MongoDB. Once data is exported you can configure team and allocate resources to sprint backlog tasks.
Team management
You need to create a group and associate it with one or more components. Association with components means the group members have corresponding expertise. After that please assign employees to group and define number of hours per sprint that employee can dedicate to group planned tasks. Please note according to agile practices it is not recommended to plan tasks on 8 hours per day basis - it is better to keep some contingency for unplanned activities. The group's capacity is calculated as sum of individual’s capacity.
Resources allocation
Agilego provides functionality similar to MS Project Resource Usage View. You can allocate resource to task dropping task from backlog into corresponding cell in the grid timeline/resource.
Gantt chart
Agilego builds Gantt chart based on block/blocked by dependency links from Jira. Task duration is calculated on resource allocations data or estimate/due data data from Jira. Also chart shows external dependencies - blockers and blocked tasks out of sprint scope.
Plan vs Actual
Agilego builds plan vs actual report that shows
- scope changes
- baseline variance: planned start/end date vs actual status, assignee, hours
Professional Services
Our team of best in class experts can solve the task of any complexity
- Eccentex
- Salesforce
- Pega BPM
- HPE MicroFocus Service Manager
- Chatbots
- AI
- Amazon AWS, HP Cloud Services, Google WS cloud migration
- BigData
- Blockchain
Software development is a craft, it's an engineering discipline, mathematics, it's a mysterious art. It's like making the whole community write poetry together. There are temperamental geniuses, tough demands, communication needs, and, at the same time, people working together create what they do not quite understand. The result is good, the result is breathtaking. Made poorly, and the result is prefabricated material. Let's write a brilliant poem together..
Technologies we use
Platforms
Desktop Platforms: Windows, Linux, MAC OSX
Mobile Platforms: iOS, Android, WinPhone
Mobile Cross Platform Expertise:
TML5 Hybrid Solution, Phonegap
Desktop Cross Platform EXPERTISE:
C++, QT framework
Technology Standards
- Java EE (Servlets, JSP, WEB Services, Apache Open Source), AJAX, JSF, Swing, Java SE, .NET, React, React Native, NodeJS
- HTML, scripting languages
- jQuery, Google Web Toolkit
Database Management Tools
- Oracle
- MS SQL Server
- MySQL
- SQLite
- PostgreSQL
- DB2 mongo DB
Languages
- Java
- Groovy
- C#
DevOps…
The magic of developed service deploying fast and easily…
But this is only a sliver of the full scope. The aim is to have the latest service version in production in time and with desired quality and reliability.
So the best DevOps has to:
- Know technologies, systems and tools (server deployment, network infrastructure and virtualization to performance tuning and monitoring including high availability issues),
- Have experience in application programming and building,
- Understand IT processes
- from development processes and techniques to continuous integration practice and IT service management,
- Be perfect not only in automation but in reporting and documenting also.
