You're about to create your best presentation ever

Get started with Prezi

Agile Sprint Demo Template Presentation

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

Agile Demo

Transcript: MS in Software Engineering 2014 to 2016 Reports plotted based on Organization/Tags of the submitted talks. Academic Project Work Experience Overland Park, Kansas Tools/Technologies Used Display a preview panel of what the emails will look like while editing them on the page. Raghu Varun Reddy Pothula Venkata Senior Systems Engineer @ Infosys Ltd Hyderabad, India (2012 to 2014) Full Stack Web Developer Intern @ Quantiacs Palo Alto, California (2015 to 2016) I learnt like comment share like comment share like comment share CollabMedi: Online Collaboration for Healthcare Professionals DevCenter Project new programming language (RUBY) to always unit test the code to use static code analyzers to work in an Agile environment to write standard and readable code Reports like comment share DevCon Submission Tool Organizer Enhancements Agile Demo like comment share Lives In Education Email Preview Panel Interests

Sprint 0 Planning

Transcript: Sprint Planning Agile Software Development with Scrum Efforts Infrastructure Process New Architecture Client Access Data Model EAI / Framework Taleo / Web Services Performance Assessment Training School Status Page Apple Awards Admin / PM Stuff October 22-November 4, 2012 Questions / Thoughts Agenda Underpants Gnomes Procedures * View .pdf presentation Sprint Planning User Stories Definition of Done Risk Define Tasks Sprint Prototyping Design Class Diagrams Sequence Diagrams Data Flow Diagrams Flow Charts Stick Figures Design Review Implement Test Sprint Review Demo Lessons Learned Intro to Agile w/Scrum & Sprint 0 Planning Agile w/ Scrum Procedures Building the Backlog Sprint 0 Planning Calendar Scrub Schedule Meetings Efforts Break down to Stories Planning Poker Additional Stories / Tasks Questions

Sprint Demo

Transcript: Key Takeaways Wrapping Up the Sprint Demo The Sprint Demo is a crucial part of the Agile development process, enabling teams to showcase their progress, gather feedback, and make necessary adjustments. Summarizing key points from the Sprint Demo presentation and preparing for the Q&A session. Agile Principles Importance of Sprint Demo Agile principles focus on customer collaboration, responding to change, and delivering working software consistently within short timeframes. Sprint Demo plays a crucial role in gathering feedback, fostering collaboration among team members, and ensuring transparency in project progress to stakeholders. Addressing Audience Queries Overview of Agile Understanding Agile Development During the Q&A session, stakeholders and team members can discuss project details, challenges, and insights, fostering a collaborative environment for continuous improvement. Agile is a project management approach that promotes iterative development and cross-functional teamwork to deliver high-quality products efficiently. Understanding Sprint Demo Agile methodology revolutionizes traditional project management by emphasizing flexibility, collaboration, and rapid iteration. Definition of Sprint Demo Sprint Demo is a showcase of the work completed during the sprint cycle, highlighting accomplishments and progress to stakeholders. Sprint Demo is a time-boxed event held at the end of a sprint where the team showcases the work completed and demonstrates the functionality to stakeholders. Engaging Stakeholders Involving stakeholders throughout the sprint process fosters collaboration and aligns expectations for successful outcomes. 1 Continuous Improvement Best Practices for Effective Sprint Demos Implementing feedback loops and evaluation mechanisms drive iterative enhancements in sprint execution and outcomes. Engaging stakeholders and promoting continuous improvement are key factors in ensuring the success of sprint demos. Allocating Resources 2 Resource allocation in sprint planning involves assigning tasks to team members based on their skills and availability. By distributing resources effectively, the team ensures a balanced workload and efficient progress towards sprint goals. Setting Goals for the Sprint Sprint Demo Sprint Planning In sprint planning, the team defines clear and achievable goals for the upcoming sprint. These goals align with the project objectives and contribute to the overall success of the sprint. Sprint planning involves setting goals for the sprint and allocating resources efficiently to achieve them. 3 6 Click to add text Improved Collaboration Benefits of Sprint Demo Sprint Demo fosters a collaborative environment where team members work closely together, share feedback, and align their efforts towards a common goal. Faster Iterations Sprint Demo enhances collaboration among team members, leading to improved communication and productivity. By employing Sprint Demo, development cycles become more efficient and iterative, allowing for quicker feedback incorporation and adaptation to changes. 4 5 Feedback Collection Sprint Execution Feedback collection during the Sprint Review involves gathering insights from stakeholders on the delivered work. This feedback loop is essential for evaluating project success, identifying areas for improvement, and ensuring alignment with client expectations for the upcoming sprints. Demonstrating Sprint Deliverables Sprint Review Challenges Faced During the Sprint Review, the team showcases the completed work items, demonstrating how they align with the sprint goals and client requirements. This presentation of deliverables helps stakeholders visualize progress and provide valuable input for future iterations. Tracking the progress of tasks and deliverables is crucial for successful sprint execution. By monitoring progress effectively, teams can identify bottlenecks early and ensure timely completion of work. Challenges during sprint execution often include scope changes, time constraints, and conflicting priorities among team members. Addressing these challenges requires effective communication, agile problem-solving, and adaptability to changing project dynamics. The Sprint Review is a crucial phase in the Agile process where teams demonstrate the completed deliverables to stakeholders and gather valuable feedback for continuous improvement. Progress Tracking Progress tracking involves monitoring task completion rates, identifying blockers, and ensuring alignment with sprint goals. Utilizing tools like burndown charts and daily stand-up meetings facilitates real-time visibility into project advancement. Thinking cap on... * Summarize each point you made * Give quick call-backs so your audience remembers * Make it clear this is the end Adding final touches... Thinking cap on... Fine-tuning... This is where your presentation starts. Provide context for your audience and make it easy for them to follow. Provide statistics, go into detail, or more

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: what we've done? what we've done? #1 IBM ODM migration to AWS using cloudformation and AWS CI/CD #2 Management internship 3 accreditation 3 video submissions 3 upcoming interview +6 new candidates Hiring process automation Automated the following tasks (first module) - Send welcome email - Send business account credentials - Zoho recruit candidate module integration- Send APN registration instructions email - Send accreditation instructions email #3 Where are we at so far ? Case study Where are we at so far ? Hiring process What will be done? Next Sprint Challenges Challenges we faced case study challenges case study Hiring process

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

Explore our templates for more presentation inspiration

World Map - Antique

Description: Impactful presentations need stunning visuals and a meaningful metaphor to show high-level concepts and the smaller details. This customizable presentation template uses a classic world map visual to help you navigate complex information while staying grounded in your presentation’s core message.

Best Executive Presentation Template to Customize | Prezi

Description: Show the big picture, zoom in on details, and explain clearly how it all relates with this Prezi executive brief or Prezi nonprofit template. The lively image and bold colors make it easy to create compelling, engaging executive brief or nonprofit presentations.

Lesson Plan - Board

Description: A well-organized lesson plan is the difference between getting things done and things getting out of hand. This vibrant, customizable, easy-to-use Prezi presentation template features a sticky note theme, so you'll be able to keep track of topics, assignments, exams, and more without missing a beat.

Report - EDU

Description: If you work in education, make your next report visually interesting and easy to navigate. The line-drawn illustrations in this edu report presentation template encourage curiosity and discovery.

Now you can make any subject more engaging and memorable

Get started with Prezi