You're about to create your best presentation ever

Agile Sprint Demo Template Presentation

Create your presentation by reusing one of our great community templates.

Agile Sprint Review

Transcript: sprint backlog: Enhancing Efficiency Burndown Chart A burndown chart or burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. A burn down chart is a run chart of remaining work. It is useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burn down charts can be applied to any project containing measurable progress over time. Next Steps In the next step, after calculating the team's efficiency, the next sprint is planned and implemented on the basis of the information gathered in Burndown Chart and with the approach of increasing functional productivity. Key goals : 1. 30% of provider tasks (port master to provider) 2. Collection Schemas Documentation 3. debug ACC mapping(duplicate) 4. Modification review and debug 5. Expose book expire time, cancellation & rate policy in booking details, voucher, TA-panel and search 6. Code review and CI/CD for Rate-gain 7. Conduct acceptance tests with Rate-gain (dependent on rate-gain) 8. CI/CD For master 9. Run portal’s reporting feature 10. Hot fix : - Option reserve debug - issue with update monitoring - Rate plan delete Sprint 1 Review sprint backlog: Tech. Team Presentation sprint goals The first sprint for the tech team to improve and debug the services and start developing features.(provider) Mission : Meet the times estimate Vision : Complete all current tasks, debug and start developing new products.(Provider)

Demo Concepts in Agile Development

Transcript: Summary of Key Takeaways Agile demo sessions yield key insights, enabling clear communication, early issue identification, and streamlined decision-making processes for project success. Continuous Improvement in Demos Fostering a culture of continuous improvement in demo practices enhances quality, efficiency, and stakeholder satisfaction in Agile workflows. Recap of Agile Demo Concepts Importance of Demo Sessions Agile demos provide a platform for stakeholders to visualize progress, validate requirements, and foster collaboration in real time. Demo sessions in Agile development ensure alignment with user needs, rapid feedback, and active stakeholder involvement for successful outcomes. Conclusion and Next Steps Unlocking the potential of Agile demos in driving collaboration, feedback, and continuous improvement in the development process. PI-5B System Demo The PI-5B System Demo will focus on presenting system functionalities and enhancements made during that stage of development. Sprint Demo 5.1 Sprint Demo 5.1 will feature already implemented and during-the-sprint committed scenarios, highlighting the iterative progress in agile development. PI-6 Demos Timeline Overview Explore the timeline of upcoming demos for PI-6, showcasing key milestones and events scheduled for demonstration. PI-6A System Demo Sprint Demo 5.3 Sprint Demo 5.3 will showcase implemented scenarios and address any remaining deltas, ensuring features are fully developed for deployment. PI-6A System Demo will consolidate committed scenarios into an end-to-end storyline, providing a comprehensive view of system capabilities developed in PI-6. PI-6B: TT Go-Live Readiness Demo PI-6B will include the TT Go-Live Readiness Demo, marking the final stage of system preparation before deployment. Best Practices for Efficiency Implementing Agile Demo Strategies Focus on not-yet-implemented Sprint scenarios to capture and communicate the implementation delta. Documenting through user stories enhances understanding and streamlines the demo process. Effective demo strategies are crucial in Agile development. Embracing best practices ensures efficient demo sessions and successful outcomes. Engagement of Process Owners Involving process owners in the demo process is essential for obtaining sign-offs and ensuring alignment with business objectives. Their input contributes to successful demo outcomes and stakeholder satisfaction. Goals and Integration The primary goal of the E2E System Demo is to offer an integrated view of the system, showcasing how customers can effectively navigate and utilize the implemented system to carry out their entire business process seamlessly. User Stories for Clarity User stories play a pivotal role in Agile demos by providing clear and concise descriptions of implementation deltas. They serve as a valuable tool for effectively communicating progress and requirements. Bundling Scenarios End of PI - E2E System Demo Efficiently bundle and present committed scenarios within a coherent narrative during the E2E System Demo to give a comprehensive overview of the project's achievements and progress. Unlock the power of E2E System Demo by showcasing the holistic view of your project's progress and functionality to a diverse stakeholder group. Participants Involve key stakeholders from diverse areas such as senior management and end-users to provide comprehensive feedback and insights during the E2E System Demo. Official E2E System Demo Engage a broad stakeholder group in a formal presentation to demonstrate how the implemented scenarios map into a cohesive storyline, illustrating the end-to-end business process. During the Sprint Demos Sprint demos in agile development play a crucial role in assessing the progress of implementation. These unofficial demos focus on yet-to-be-implemented scenarios and aim to work out implementation deltas documented by user stories. Involvement of Process Coordinators and Process Owners Unofficial Demos in Current Configuration Current configuration demos during sprints are crucial working sessions. They provide a platform for SAs and SMEs to evaluate scenarios that are not yet implemented, ensuring that necessary preparations are made for upcoming sprint and system demos. Process coordinators and owners play an active role in informing process owners about any necessary harmonization decisions during these unofficial demos. Their involvement ensures alignment and readiness for upcoming official demo milestones in the agile development process. Goals of Working Sessions Focus on Not Yet Implemented Sprint Scenarios During the sprint demos, the focus is on scenarios that have not been implemented yet. This allows the team to identify potential gaps in the process and address them proactively through collaborative working sessions. The primary goals of these working sessions are to define the implementation delta by documenting user stories and ensuring that scenarios are prepared for upcoming formal

Sprint Demo

Transcript: Ini2Sql Script use vmussd; -- getting the service code id SELECT @ServiceCodeId:=Id FROM ussdServices WHERE ServiceCode = '{0}'; -- disabling old revision SELECT RevisionId INTO @oldRevId FROM Revisions WHERE ServiceCodeId = @ServiceCodeId AND IsActive = 1; UPDATE Revisions SET IsActive = 0 WHERE RevisionId = @oldRevId; -- Inserting a new revision, revision id will be equal to the latest insert id INSERT INTO Revisions (ServiceCodeId, Description, DateCreated, DateActivated, IsActive) VALUES (@ServiceCodeId, '{1}', NOW(), NOW(), 1); -- get the new revision id SELECT last_insert_id() INTO @newRevId; -- Insert new revision id and the content of the ini file into the USSDApps table INSERT INTO USSDApps (RevisionId, AppContents) VALUES (@newRevId, """ Purpose? Jenkins Integration /** * Deletes cookie matching <b>name</b>.<br> * <br> * If the cookie is not found, nothing happens<br> * * @param name * The name of the cookie to delete. */ @RobotKeyword @ArgumentNames({ "name" }) public void deleteCookie(String name) { browserManagement.getCurrentWebDriver().manage().deleteCookieNamed(name); } dos2unix app.ini && sed -i.orig 's/\"/\\"/g; s.\\{.\\\\{.g; s.\\\}.\\\\}.g' app.ini && pbcopy < app.ini Script SQL Template Test Libraries Script Snippet Java Support dosCmd = subprocess.Popen(['dos2unix', '{0}'.format(abs_file_path)], stdout=subprocess.PIPE, stderr=subprocess.PIPE) sedCmd = subprocess.Popen(['sed', '-i.orig', 's/\"/\\"/g; s.\\{.\\\\{.g; s.\\\}.\\\\}.g',"{0}".format(abs_file_path)], stdout=subprocess.PIPE, stderr=subprocess.PIPE) try: with open(abs_file_path, 'r') as iniFile: data=iniFile.read() except IOError: print "Error opening the .ini file" sys.exit() output = sqlTemplate + '"' + data + append with open("{0}".format(args.outputFile), 'w') as outFile: outFile.write(output) *** Settings *** Library Selenium2Library Suite Setup Go to homepage Suite Teardown Close All Browsers *** Variables *** ${HOMEPAGE} http://google.com ${BROWSER} firefox *** Test Cases *** Google devops and find wiki Google keyword devops wikipedia https://en.wikipedia.org/wiki/DevOps *** Keywords *** Google keyword [Arguments] ${searchkey} ${result} Input Text id=lst-ib ${searchkey} Click Button name=btnG Wait Until Page Contains ${result} Xpath Should Match X Times //a[text()='DevOps - Wikipedia'] 1 Click Element xpath=//a[text()='DevOps - Wikipedia'] Wait Until Page Contains Element xpath=//a[text()='Requirements'] Wait Until Element Is Visible xpath=//a[text()='Requirements'] Xpath Should Match X Times //a[text()='Requirements'] 1 Capture Page Screenshot Click Element xpath=//a[text()='Requirements'] Go to homepage Open Browser ${HOMEPAGE} ${BROWSER} Ansible Sprint Demo Robot Framework

Sprint Demo

Transcript: Thank You. 3. Api bug fixes sheet. 1.Code Analysis. Live Apk: The testing was done in on all of 3 Apk bug were fixes. Giving our contribution for testing apk. List of specific bugs that were discovered on the live APK. Brief description of each bug and its impact on the user experience. Evaluating and improving code quality through systematic examination. Higher code quality. Improved team collaboration. Reduced bug count. Knowledge sharing and mentoring. Areas of improvement identified 4.Commenting the code for more understanding. 2.profile showing 100% Before the recent code modification, the profile percentage displayed a value of 95%. The issue was identified and addressed through a change in the codebase. The modification ensures that the profile percentage accurately reflects the completeness of the user's profile, and as a result, it now shows 100%. Clarity: Provides clear guidance on what aspects of the code to comment on. Organization: Maintains a structured approach to commenting, covering essential areas. Completeness: Ensures all critical aspects of the code are adequately documented. Readability: Creates a clear and understandable framework for documenting code. Project Architecture. Sprint B. 1Gen Nano Sagar Ahire. Shayuri Harpale. Omkar Jadhav. Guided By: Sahil Rana and our team members. Afterwards, we make API requests, such as adding specific information to a particular API, followed by verifying the corresponding collection in the database and utilizing specific IDs to validate the database entries We need to review the project code flow, examine specific API endpoints, and verify the collection names used within the APIs After reviewing the code flow and APIs, we proceed to test the APIs on Swagger by retrieving and adding data through API calls.

Sprint Demo

Transcript: Questions Sprint Demo Employer Servery Introduction Intro Q4 TARGETS Targets 45 days gone 46 days to go Sprints Sprints AIR Goal: Solved? Results: Salto Portale - Merge the csv/xls export rights into one. - Rewrites in the import functionality Yes, its solved! Simpler Rights (Vaporize!) Goals: Solved? Results: A-Team Local development environment similar to production, using Yes, it's solved! With a few commands it is now possible for developers to start a complete development environment on their local machine without the requirement to have the knowledge about the underlying system. This will make it possible for developer to focus on their work without the delays of development on the internal servers Goal: Solved? Results: De Normalo's Dynamic Filters Overview sub-pages Refactoring Yes, its solved! Better User Experience More complete New Framework Goals: Solved? Results: Unicorn API: Dashboard messages for the app API: Suppliers email for the app Yes, its solved! Enable Appic toshow Dashboard Msg and ask opinion of a supplier Goal: Solved? Results: Switch between multiple accounts Show notes with invoices Yes, its solved! No need to repeatedly log out and log in! Better informed users Better App, less need to use the Web! Goal: Solved? Results: Appic Firebolt Focus on Front End + Visit of Claudia & Tom Ask for password when changing user data Yes, and not yet Better alignment with front end Groundworks for password required action Goal: Solved? Results: Flux Make the overview pages responsive for mobile screens Not yet, still finalizing Designs for a mobile and touchscreen friendly webapp Goal: Solved? Results: 1 New Products 2 Training for new products Q 1 Q 2 Q 3 Q 4 3 Top performers Name Job title Name Job title Name Job title

Now you can make any subject more engaging and memorable