How Our Agile Team Works?
GeakMinds has executed industry leading agile practices to quite a lot of our clients around the globe. Our project managers are qualified agile practitioners and carry the best agile practice of GeakMinds into the project. Our scrum masters work with the product owner to recognize which sort of agile methodologies such as scrum, XP can be used for the project.
Our project managers and team works by categorizing the top agile tool such as LeanKit, Jira Rally etc. Our qualified scrum masters at GeakMinds lead the release and sprint planning in the presence of the complete project team. During this meeting, user stories are reviewed, sizes are valued. They work with the product owner to craft and place in order the user stories before the time bound sprint commences.
A Daily stand-up meeting is piloted by our scrum masters for the entire project team, product owner and subject matter experts. This meeting is conducted proficiently by concentrating on user stories and team members who work on it. Three questions are asked during this meeting: what did you do yesterday, what will you do today, are they any impediments in your way. Any follow-up or thoughts are carried on in the designated team areas or war rooms.
We also use tools such as wire frames to inspire productive design sessions. After the user stories are developed and DONE, demo is given to the product owner for the final deployment approval.
Once all the user stories are acknowledged and deployed into production, our expert scrum masters conduct a retrospective meeting where the team discusses about the sprint: what went well, what went wrong and what we could do differently to make the next sprint more productive.
- Business Requirement Analysis:
Requirement analysis phase is equivalent to examining and brainstorming what the product/service requires from and out of the development. Examples include overall features discussions, architecture planning, workflow discussions and product/service innovation.
- Design and Prototype:
In this phase, we define the Scope of work to be done, which will have all the requirements well-defined for the product/service.
- Iterations and Feedback:
During the software development, iterations are required to test the code as well as get opinion from the customer on progress. Feedback from the customer can include: mockups, front-end designs, and usability.
- Identify defects and Resolve Bugs:
Bugs and defects always occurs in the software development process. It is significant that there are good Quality Assurance principles to remove recurrent issues.
- Production and Technical Support:
The developed software application is finally deployed in the live environment. Once it is deployed, a support plan will be in place for maintenance and support in resolving possible future issues.
Lean methodology in agile eliminates waste by choosing only the truly valuable features for a system, ranking those selected, and deploying them in small batches. It highlights the speed and efficiency of development workflow, and depends on speedy and consistent feedback between programmers and customers. Lean uses the idea of work product being “pulled” via customer request. It centers decision-making authority and ability on individuals and small teams, since research shows this to be faster and more efficient than traditional methodologies. Lean also focusses on the efficiency of the use of team resources, trying to make certain that everyone is productive as much of the time as possible. It focusses on parallel work and the least possible intra-team workflow habits. Lean also intensely endorses that automated unit tests be written at the same time the code is written.
- Identify value: We define value from the customers’ perspective and express that value in terms of a specific product or service.
- Map the value stream: We map all the steps from value added to the non-value added, that brings a product or service to the customer.
- Create flow: We create a continuous flow of products, services and information from end to end throughout the process.
- Establish pull: We pull only what is required when requested by the end customer or the next step in a process. Value is pulled through a process rather than being created in batches or as capacity constraints allow as this minimizes overproduction, stocks and ultimately working capital.
- Seek perfection: We completely eliminate waste so all activities create value for the customers by breakthrough and continuous improvements and delivery.
Agile Tools We Use
- LeanKit – LeanKit uses a cloud-based whiteboard metaphor for mapping out organization processes. Cards represent work items, and status updates are provided. Our teams that use LeanKit can see workload distribution and export historical data.
- Jira Agile – Jira is a popular tool for tracking product development, enabling teams to organize issues, assign work, and follow team activity. Jira Agile provides add-on facilitates like key agile strategies, including the development of user stories, building of sprint backlogs, and visualization of team activities.
- Scrum – Scrum helps our development teams manage backlog, releases, and sprints. It features burndown charts and a management dashboard, and it tracks time spent coding features and fixing bugs. It includes other useful collaborative tools, such as a wiki and bug tracker.
- Rally – This cloud-based agile lifecycle management platform scales to an unlimited number of teams and features custom pages and dashboards to automate various development processes.
- Planbox – Planbox tracks progress via burndown charts, integrates customer feedback, and is aimed at a wide range of personnel.
Why We Implement SAFe?
InfoFaces’ Agile Practice helps companies to put into practice and speed up agile adoption that leads to improved workflow, revenue and business. Our Agile expertise have industry-leading experience that includes a profound understanding of how Agile impacts Business-IT alignment, Release Planning, Quality, Cultural and Behavioral Change.
Scaled Agile gives us a framework for extending our process to:
Larger scope items in parallel work streams
- Provides a middle layer of scope items between user story (very small) and release (very large).
- Requirements are described as minimally as possible.
Over longer time increments
- A program increment cadence continues in parallel with sprint cadence, allowing a quarterly long-view planning process. The program increment (PI) is the largest plan-do-check-adjust (PDCA) learning cycle in SAFE. A Program Increment is to the Agile Release Train (or Value Stream) as an iteration is to the Agile: a cadence-based interval for building and validating a full system increment, demonstrating value and getting fast feedback.
Across multiple delivery teams
- Program increments are well-defined for the team as a whole rather than specific scrum teams.
Sprint practices and ceremonies are Scaled
- Backlog of scope items (features) is maintained and prioritized.
- Team obliges to deliver a set number of scope items in a time boxed increment.
- Team works collaboratively to deliver scope items during the course of the increment.
- At the end of the increment, we take time to reflect and adjust its process, enabling future success.
SAFe At Team, Program And Portfolio Level
The Team level provides a process model for agile teams based on Scrum and XP practices. At the Program level, the efforts of multiple agile teams are integrated to deliver larger value releases to the enterprise. At the Portfolio level, programs are aligned to business strategy and investment intent.
SAFe – Team Level
- Valuable, fully-tested software increments every two weeks.
- Empowered, self-organizing, self-managing cross-functional teams.
- Teams operate under program vision, architecture and user experience guidance.
- Scrum project management and XP-inspired technical practices.
- Value delivery via User Stories.
SAFe – Program Level
- Self-organizing, self-managing team of agile teams.
- Working, system increments every two weeks.
- Aligned to a common mission via a single backlog.
- Common sprint lengths and estimating.
- Face to face release planning cadence for collaboration, alignment, synchronization and assessment.
- Value delivery via Features and Benefits.
SAFe – Portfolio Level
- Centralized strategy, decentralized execution.
- Lean-agile budgeting empowers decision makers.
- Kanban systems provide portfolio visibility and WIP limits.
- Enterprise architecture is a first class citizen.
- Objective metrics support governance and Kaizen.
- Value description via Business and Architectural Epics.
How We Implement SAFe?
The significant SAFe practice used by InfoFaces is centered on the program increment (PI):
- Six sprints in length, time-boxed
- Scope items are described as business objectives and features
- Commitments are made on a quarterly basis by InfoFaces’ team as a whole at program increment planning meeting. Increment planning meetings are quarterly team activities that replicate sprint-level activities on a larger scale
- Retro the prior increment
- Introduce the proposed scope of the new increment
- Team validates scope
- Size high-level stories
- Schedule high-level stories into sprint-by-sprint plans
- Identify dependencies and risks that need follow-up work
- Make a commitment