Menu

Optimizing Lean Agile Process: A Retrospective Approach

Category Data Engineering

Lean agile process is a very effective way to handle any project. The methodology helps eliminate unnecessary processes, reducing ambiguity and allowing the team to utilize their time optimally in developing an effective software with better functionality. With lean agile process, team is better equipped to focus on objectives, improve productivity and deliver superior value to the customers.

Few of the building blocks for implementing lean agile principles are grooming the user stories and the functionalities or epics by understanding acceptance criteria, prioritizing, and conducting retrospectives. While grooming is an important part of the process, retrospective is equally imperative that enables the team to understand what went well and what did not. The key objective of retrospective meeting is to understand the drawbacks of the process and make necessary changes. However, there’s no right or wrong way for retrospection.

Retrospection

In this post I am sharing our approach to retrospective meeting that helped my team during the development process. My team is a standard scrum team comprising software developers, test engineers, data engineers and analysts.

The initiation

We followed a process where the first two sprints were development sprints and we started testing from the third sprint. While we conducted retrospective meeting after the end of each sprint, most of it looked good when the code was not tested.

Retrospective meeting led to greater discussions from the third sprint onwards. We also had to dig deeper into the first sprint as the test engineers had more insights about their findings from the sprint-1. This resulted in code re-work in order to fix the bugs altering the velocity of the following sprints.

Initial process included:

Sprint-1: Develop

Sprint-2: Develop

Sprint-3: Develop + Test + Bug fixes

Sprint-4: Develop + Test + Bug fixes

Depending on the severity of the bugs, the velocity varied from sprint to sprint because the priority of the client differed. In some sprints, we were expected to fix key functionality bugs first whereas in certain sprints we had to complete coding on priority.

The issue with this process was that every time the client engineers produced better results than we did with the same set of data. While customer expected better results in each demo, test engineers were out of pace and didn’t have the clarity on what test cases to write.

To address this challenge we decided to make some changes to the process in order to produce better outcome. The changes made to the process include:

  1. As soon as we receive the requirements, developers would make assumptions
  2. These assumptions need to be discussed in sprint meeting at the beginning of the sprints with the team and key stakeholders. This helps clarifying as many doubts as stakeholders may have right at the start of the sprint.
  3. Project managers to do risk analysis based on these assumptions
  4. Test engineers to get involved right from the Sprint-1. Developers should provide the expected data output according to their assumptions to test engineers for them to write relevant test cases.
  5. Not to conduct demo of our work on fixed days but showcase when we develop or reach a significant stage in our model/approach.
  6. During the sprint, whenever we have any doubt in our assumption, discuss it with the related stakeholders because as we know, no result is wrong with respect to data or data science.
  7. Developers should perform unit testing followed by moving the code into test environment and during the testing process, developers should optimize the code (which is an important step added to the process).
  8. End of each sprint, justify the assumptions made, to the stakeholders and demonstrate the outcome.

Here is an example of the scenario where we implemented the preceding changes. The code that we were writing for one of the sprints had to perform the following:

  1. Fetch 100 million records by reading line by line and channelize the data into a platform — Each record took 50 bytes (5 kb in total) and it took 2.3 minutes to fetch all the records
  2. On the platform we cleanse the data and perform some mathematical operations through an API in order to produce the predictive algorithms

We were using certain streams in order to work with the data that included:

InputStreamReader: It fetches data from the coding platform, converts byte into character and passes onto BufferedReader

BufferedReader: It reads the character streams from InputStreamReader and deploy the data sequence into the platform

New process implementation

The change in the process helped us in several ways. As we made assumptions we also provided test cases to the test engineers right at the beginning. This made it easy for them to understand the expected output and write better test cases while clarifying doubts as and when required helped optimize time and effort. We conducted the demo every time we reached a significant stage improving our client’s experience. On the other hand, as we kept our key stakeholders informed throughout the process making it easy to justify our assumptions in retrospective meetings.

Apart from this, we accelerated the process of fetching data by optimizing code. The changes made were as follows:

1. We improvised the way we read data from files using specific lightweight streams, which consumes less memory (such as FileInputStreams instead of InputStreamReaders)

2. Made single statement query and set the connection autocommit to false

3. Unit test results showed us that they were unnecessary code which increased the timelapse and we could avoid the boundary conditions which were not needed

We also deployed coding into the test environment. While the test engineers tested the code, developers started to optimize the code further. We re-designed the architecture — fetched first 1 million records using optimized SQL and then fetched next chunk in parallel with different set of code. We also used Byte channels to read the data and during the process we continually cleared the buffer in the code which helped boost the speed.

Lean agile methodology for continuous improvement

We incorporated these changes at the optimization stage while testing was done parallelly that enabled us to save time and improve efficiency. It helped reduce coding time by 70% (it took total 69 seconds to fetch the entire datasets) and man hours by 35%. In addition to this, we built a cross functional team that allowed us to think from various perspectives, facilitating knowledge sharing and enhancing productivity.

Combining lean and agile principles helps take advantage of key elements of both the methodologies and customize them to meet project-specific requirements. It allows to integrate continuous improvement and follow best development practices enabling the team to optimize performance and deliver value.

Let us know how you liked the post and share your experience of using lean agile methodologies, we love to hear from our readers.

Recommended Reading

Explore our insightful articles, whitepapers, and case studies that delve deeper into the latest industry trends, best practices, and success stories. Gain valuable knowledge and stay informed about the ever-evolving landscape of digital transformation.

Navigating The Two Major Data Trends in 2024

As the data landscape continues to evolve rapidly, businesses are compelled to stay abreast of emerging trends to maintain competitiveness. In the year 2024, two prominent trends are poised to redefine data analytics: the proliferation of Generative AI and the adoption of modern data contracts. These trends not only reshape how organizations utilize data but also underscore the importance of ethical considerations and robust governance in data management. This article explores these trends in-depth, providing insights into effective strategies for implementation and the implications for businesses navigating the data landscape.Trend #1: The Ascendancy of Generative AIGenerative AI, characterized by its ability to create new content autonomously, has gained significant traction across industries. The advent of large language models (LLMs) has propelled Generative AI into the mainstream, with tech giants like Microsoft, Google, and Meta integrating Generative AI capabilities into their products. As businesses increasingly rely on AI-driven insights, Generative AI is poised to become an indispensable tool for enhancing productivity and driving innovation.Strategy for Effective Implementation:To leverage Generative AI effectively, businesses must develop a comprehensive strategy tailored to their specific needs and objectives. This strategy should encompass several key components:Identifying suitable use cases:Organizations should identify areas where Generative AI can augment existing processes and generate tangible value. Whether it’s automating content creation, personalizing customer experiences, employee training, or optimizing business operations, identifying the right use cases is essential for maximizing ROI.Comprehensive employee training:Implementing Generative AI requires upskilling employees to ensure they can effectively utilize AI tools while adhering to ethical guidelines and best practices. Training programs should cover topics such as data privacy, bias mitigation, and ethical AI usage to foster a culture of responsible AI adoption.Strong data governance:Robust data governance is critical for ensuring the accuracy, security, and ethical usage of AI-generated insights. Organizations must establish clear guidelines and protocols for data collection, storage, and usage to mitigate risks associated with data misuse or bias.Managing costs and licensing:While Generative AI offers immense potential, it also comes with significant costs, both in terms of technology investments and licensing fees. Organizations must develop a cost-effective strategy for scaling AI initiatives while ensuring compliance with budgetary constraints.Balancing automation and human judgment:While AI-driven insights can enhance decision-making processes, it’s essential to strike a balance between automation and human judgment. Human oversight is crucial for interpreting AI-generated insights, identifying biases, and ensuring ethical decision-making.Ethical considerations:As AI becomes increasingly integrated into business operations, organizations must prioritize ethical considerations and accountability. This includes addressing issues related to data privacy, algorithmic bias, and the potential societal impact of AI-driven decisions.Trend #2: Adoption of Modern Data ContractsModern data contracts have emerged as a solution to streamline data usage and sharing, effectively addressing the challenges associated with broken data integrations and communication gaps between application and analytics teams.Structured Data Interactions:Modern data contracts represent a paradigm shift in how organizations manage data interactions. Unlike traditional contracts, which are static and cumbersome to maintain, modern data contracts are dynamic agreements that evolve with changing data requirements and business needs.Integration into workflows:By integrating data contracts into existing workflows and development processes, organizations can ensure seamless data interactions across disparate systems and applications. This integration enables teams to collaborate more effectively, reducing friction and improving data quality and consistency.Implementation Strategies:Implementing modern data contracts requires a strategic approach focused on collaboration, standardization, and automation. Key strategies include:Developing clear standards:Organizations should establish clear standards and guidelines for data contracts, outlining key parameters such as data formats, schemas, and validation rules. These standards help ensure consistency and interoperability across data systems and applications.Instituting change controls:Change management processes are essential for managing versioning and ensuring smooth transitions between data contract iterations. By implementing robust change controls, organizations can minimize disruptions and maintain data integrity throughout the contract lifecycle.Training and tools:Equipping teams with the necessary training and tools is crucial for successful data contract implementation. Training programs should cover topics such as contract management, data governance, and compliance, while tools such as data modeling platforms and contract management software can streamline the contract development and deployment process.As businesses navigate the complexities of the data landscape in 2024, adapting to the rise of Generative AI and modern data contracts is essential for driving innovation and maintaining competitiveness. By developing comprehensive strategies for AI adoption and data governance, organizations can harness the transformative power of Generative AI while ensuring ethical and responsible data usage. Likewise, embracing modern data contracts enables organizations to streamline data interactions, improve collaboration, and enhance data quality and consistency. By embracing these trends and implementing best practices, businesses can unlock new opportunities for growth and success in the digital age.

Learn More >

The Journey from System Admin to DevOps Superstar

According to a report by the Economic Times, when organizations cultivate a better work environment, the overall experience improves exponentially. They find true meaning in their jobs by prioritizing employees’ mettle, exceeding expectations, and work allocation.Employees seek exposure and opportunities in their jobs. By building productivity and customer satisfaction they enhance their portfolio.Radhakrishnan one of our DevOps superstars, has contributed with his service and time for over 8 years. To commemorate this everlasting relationship we got into a candid conversation with him. Here’s what he had to say about his journey before and with Nineleaps.Radhakrishnan is originally from a small town near Bengaluru, Hosur. After completing his MBA, his interest developed in computers and networking. He successfully gained appropriate knowledge by undertaking network courses and embarked on a journey to becoming a system admin. He enjoyed working for various companies as a system admin.Then came Nineleaps which gave new horizons of opportunities to his mettle. When we asked him about his transition from a system admin to a DevOps engineer, he fondly remembered a quote given to him by our CEO on the day of his selection.“You are on the flight now, just fly,” — Divy Shrivastava.And, so he did.Divy’s words of confidence boosted his resolve. The walk towards DevOps became a sprint, as multiple iterations of knowledge and experience suffused him. The arena of his work leaped and much to his admiration, he realized DevOps to be his passion and soul.Right from the get-go, an intensive training regimen, honing his skills, immersing himself in countless hours of study, and shadowing esteemed senior members of our organization he grasped the crucial importance of comprehending tasks and prioritizing them effectively. Driven by an unwavering desire to learn and prove his mettle, his transition from a system admin to a DevOps maestro was seamless. Multiple training sessions helped him get a deeper understanding of internal and external projects as well as the product, giving him never-to-dull confidence.Learning and development, knowledge transfers, and peer learning are certainly at the core of Nineleaps which helped him become the super engineer he is today. These trainings were both from the client’s side as well as in-house learning at Nineleaps.“In my opinion what sets Nineleaps apart is our dynamic and flexible approach to projects, with extensive focus on Agile methodology we are trained and nourished to build quality solutions for our clients, and also are facilitated with high-tech exposure by working with industry giants and rewarded with the utmost respect and growth opportunities.”To understand more closely we asked him about the challenges he faced at times, and according to him, documentation was a challenge. He feels all the work that the employee is doing must be documented and organized in a proper way as it will help them in the future. He also informed about instances where a person working on a specific problem might face similar challenges later in the same week and not be able to recall what the solution was properly, in such cases documenting everything became important. The organization’s culture was very open and asking questions or requesting help was never an issue which facilitated collaboration in resolving such challenges.Nineleaps became the crucible to test his mettle and with each strike of the hammer, a superstar was born.

Learn More >

Performance Testing Trends: Future of Software Optimization

Performance testing is an integral part of the software development lifecycle as it helps determine the scalability, stability, speed, and responsiveness of an application as compared to the workload given. It is not a standalone process and should be run throughout the software development process.It serves the purpose of assessing various aspects of an application’s performance, such as application output, processing speed, data transfer velocity, network bandwidth usage, maximum concurrent users, memory utilization, workload efficiency, and command response times. By evaluating these metrics, performance testers can gain valuable insights into the application’s capabilities and identify any areas that require improvementUsing AI to automate testing:Performance testing encompasses various stages, each posing unique challenges throughout the testing lifecycle. These challenges include test preparation, execution, identifying performance bottlenecks, pinpointing root causes, and implementing effective solutions. AI can help reduce or even eliminate these differences. AI-powered systems can handle the mountains of data collected during performance testing and be able to produce efficient and accurate analyses. AI can also identify the sources of performance slowdowns in complex systems, which can otherwise be tedious to pinpoint. With AI-driven automation, performance testers can streamline the testing process, ultimately saving time and resources while ensuring reliable results.Open Architecture:Performance testing, which evaluates how well a system performs, is undergoing a significant shift away from relying solely on browser-based evaluations. Instead, internet protocols like TCP/IP are being adopted for comprehensive performance monitoring. This approach emphasizes the need for system components to work together harmoniously while assessing their performance individually. The integration of cloud-based environments has become crucial, as cloud computing is an integral part of modern technology infrastructure. Cloud-based environments provide a flexible and reliable platform that enables seamless integration and coordination of various components, ultimately leading to enhanced system performance. It is crucial to prioritize comprehensive performance testing, which involves evaluating individual component performance, managing loads, monitoring in real-time, and debugging, to ensure optimal system performance.Self Service:When adopting the aforementioned trends, it’s essential to consider practical implementation tips for successful outcomes. For instance, performance engineers can use AI-powered tools to analyze performance data more effectively, leading to more accurate and actionable insights. Integrating cloud-based solutions can provide the flexibility and scalability required for modern performance testing demands. As stakeholders implement these trends, the collaboration between development, testing, and IT operations teams becomes crucial for successful integration and improved application performance.SaaS-based Tools:Testers can now easily set up and execute tests at cloud scale within minutes, thanks to the convergence of self-service, cloud-based testing, SaaS, and open architecture. Unlike older desktop-based tools that demand extensive setup, the emerging tools simplify the process with just a few clicks. Furthermore, these modern technologies offer seamless interoperability, significantly enhancing performance capabilities.Changing Requirements:In classic app testing, testers had to make educated guesses about the software’s use and create requirements and service-level agreements accordingly. However, in DevOps-oriented environments, performance requirements are seen as dynamic and evolving. Traditional requirements are now driven by complex use cases, accommodating different user experiences across various devices and locations. Performance engineering plays a critical role in continuously monitoring systems and proactively identifying and resolving issues before they can negatively impact customer retention or sales.Sentiment analysis:Monitoring production provides insight into server response times but does not capture the true customer experience. Synthetic transactions, on the other hand, simulate real user actions in production continuously. They can range from basic interactions like logging into an e-commerce site and adding products to a cart, to more complex transactions that track performance end to end without actually completing real orders or charging credit cards. Tracking the actual user experience is crucial for identifying bottlenecks, delays, and errors in real-time, as some issues may go unreported by users. Sentiment analysis is a powerful technology that evaluates customer responses based on emotions, providing valuable insights from customers’ reactions expressed in plain text and assigning numerical sentiment scores.Chaos Testing:Chaos testing is a disciplined methodology that proactively simulates and identifies failures in a system to prevent unplanned downtime and ensure a positive user experience. By understanding how the application responds to failures in various parts of the architecture, chaos testing helps uncover uncertainties in the production environment. The main objective is to assess the system’s behavior in the event of failures and identify potential issues. For instance, if one web service experiences downtime, chaos testing ensures that the entire infrastructure does not collapse. This approach helps identify system weaknesses and addresses them before reaching the production stage.Conclusion:As software development continues to evolve, performance testing must keep pace with emerging trends and technologies. By leveraging AI-driven automation, open architecture with cloud integration, and practical implementation tips, stakeholders can optimize their performance testing processes to deliver high-performing and responsive software applications. Real-world examples and a focus on key performance metrics ensure that these trends are not only understood but effectively implemented to achieve the desired outcomes. Embracing these trends empowers software development teams to elevate the user experience, enhance customer satisfaction, and drive business success.

Learn More >

Ready to embark on a transformative journey? Connect with our experts and fuel your growth today!

Explore Now