The presentation covers one of the Agile Methodologies. Dynamic Systems Development Method (DSDM) is a framework based originally around Rapid Application Development (RAD).DSDM recognises that projects are limited by time and resources, and plans accordingly to meet the business needs.
This document discusses planning for a software project management session. It covers phases in software development in detail, including lifecycle planning and project plans. It discusses primary planning steps and key planning documents like the Software Development Plan and Risk Management Plan. It also outlines key product documents produced during planning like the Statement of Work, Requirements Document, and Design Specification.
The document discusses the use of a DACUM (Developing A Curriculum) process to develop a curriculum for software engineering at NASA. It provides details on the multi-phase DACUM process used, including conducting workshops with expert software engineers to identify key job tasks and requirements, and subsequent workshops to develop a curriculum map that specifies where various topics should be taught. It summarizes the history of applying this process for NASA's software engineering curriculum.
The document provides an overview of JUMP (Scalable, Successful Approach to Software Project Management). It discusses key aspects of the JUMP methodology including its iterative process, roles, phases (inception, elaboration, construction, transition), reviews, artifacts, tools, best practices, and metrics for measuring success. The goal of JUMP is to achieve project commitment and consensus through formal reviews at key milestones to align projects with organizational directives.
Other software processes (Software project Management)Ankit Gupta
This document discusses various other processes that support software development processes, including project management, inspection, configuration management, change management, and process management. It provides details on the typical roles and responsibilities of a project manager, including planning, monitoring and controlling the project, and facilitating communication. It also discusses different meeting types, communication modalities, risk management processes, and the importance of communication facilitation for successful project execution.
Deze presentatie beschrijft een praktische implementatie van het gebruik van Nesma functiepunten in Agile deliveries. Deze presentatie is gepresenteerd door Richard Sweer van Infinity tijdens de webinar Afrekenen met functiepunten. Voor meer info: www.nesma.org; conference@nesma.org.
The document discusses several key challenges in software engineering (SE). It notes that SE approaches must address issues of scale, productivity, and quality. Regarding scale, it states that SE methods must be scalable for problems of different sizes, from small to very large, requiring both engineering and project management techniques to be formalized for large problems. Productivity is important to control costs and schedule, and SE aims to deliver high productivity. Quality is also a major goal, involving attributes like functionality, reliability, usability, efficiency and maintainability. Reliability is often seen as the main quality criterion and is approximated by measuring defects. Addressing these challenges of scale, productivity and quality drives the selection of SE approaches.
This document provides an overview of various topics related to software project management. It begins with a list of suggested topics for discussion, such as challenges specific to software projects, quality measurements, and best practices in Pakistan. It then covers aspects of the software development lifecycle from planning and requirements through deployment and maintenance. Different project models like waterfall, evolutionary prototyping, and spiral development are described along with their advantages and disadvantages. Finally, it touches on using commercial off-the-shelf software.
Software metrics involve collecting measurements related to software development processes, projects, and products. There are different types of metrics including process, project, and product metrics. Process metrics measure the software development lifecycle, project metrics measure team efficiency, and product metrics measure quality. Metrics can also be private, used by individuals, or public, used to measure teams and processes. Size-oriented metrics are computed based on the size of the software, often expressed in lines of code.
This document discusses planning for a software project management session. It covers phases in software development in detail, including lifecycle planning and project plans. It discusses primary planning steps and key planning documents like the Software Development Plan and Risk Management Plan. It also outlines key product documents produced during planning like the Statement of Work, Requirements Document, and Design Specification.
The document discusses the use of a DACUM (Developing A Curriculum) process to develop a curriculum for software engineering at NASA. It provides details on the multi-phase DACUM process used, including conducting workshops with expert software engineers to identify key job tasks and requirements, and subsequent workshops to develop a curriculum map that specifies where various topics should be taught. It summarizes the history of applying this process for NASA's software engineering curriculum.
The document provides an overview of JUMP (Scalable, Successful Approach to Software Project Management). It discusses key aspects of the JUMP methodology including its iterative process, roles, phases (inception, elaboration, construction, transition), reviews, artifacts, tools, best practices, and metrics for measuring success. The goal of JUMP is to achieve project commitment and consensus through formal reviews at key milestones to align projects with organizational directives.
Other software processes (Software project Management)Ankit Gupta
This document discusses various other processes that support software development processes, including project management, inspection, configuration management, change management, and process management. It provides details on the typical roles and responsibilities of a project manager, including planning, monitoring and controlling the project, and facilitating communication. It also discusses different meeting types, communication modalities, risk management processes, and the importance of communication facilitation for successful project execution.
Deze presentatie beschrijft een praktische implementatie van het gebruik van Nesma functiepunten in Agile deliveries. Deze presentatie is gepresenteerd door Richard Sweer van Infinity tijdens de webinar Afrekenen met functiepunten. Voor meer info: www.nesma.org; conference@nesma.org.
The document discusses several key challenges in software engineering (SE). It notes that SE approaches must address issues of scale, productivity, and quality. Regarding scale, it states that SE methods must be scalable for problems of different sizes, from small to very large, requiring both engineering and project management techniques to be formalized for large problems. Productivity is important to control costs and schedule, and SE aims to deliver high productivity. Quality is also a major goal, involving attributes like functionality, reliability, usability, efficiency and maintainability. Reliability is often seen as the main quality criterion and is approximated by measuring defects. Addressing these challenges of scale, productivity and quality drives the selection of SE approaches.
This document provides an overview of various topics related to software project management. It begins with a list of suggested topics for discussion, such as challenges specific to software projects, quality measurements, and best practices in Pakistan. It then covers aspects of the software development lifecycle from planning and requirements through deployment and maintenance. Different project models like waterfall, evolutionary prototyping, and spiral development are described along with their advantages and disadvantages. Finally, it touches on using commercial off-the-shelf software.
Software metrics involve collecting measurements related to software development processes, projects, and products. There are different types of metrics including process, project, and product metrics. Process metrics measure the software development lifecycle, project metrics measure team efficiency, and product metrics measure quality. Metrics can also be private, used by individuals, or public, used to measure teams and processes. Size-oriented metrics are computed based on the size of the software, often expressed in lines of code.
The document discusses assessing maturity models PMI/OPM3 and CMMI within the context of the COBIT framework. It provides an agenda for an assessment including analyzing the approaches, identifying gaps, and recommending next steps. It describes the models and compares them, noting that while CMMI focuses on software engineering, OPM3 focuses on project management. The approach outlined analyzes the models' coverage within COBIT domains, assesses gaps, and recommends quantified next steps for gap closure.
Business Analyst Requirements Management Mark Borowski
The document discusses the importance of requirements management for business analysts and agile development. It addresses common myths about agile not needing formal requirements. Effective requirements definition includes types, abstraction levels, and best practices like traceability. Stories are discussed as a form of agile requirements but often need further elaboration. Requirements still matter in agile and need to be well-structured, organized, and linked to other artifacts to ensure quality and manage changes.
Process for requirement identification & development in software developmentRohana K Amarakoon
In this presentation, I explain about the best full process of requirement identification to final software delivery through following steps
1. Requirement identification
2. Elaboration of requirement
3. Requirement prioritisation
4. Agile software development
This document discusses various process models for software engineering:
- The waterfall model defines sequential phases of requirements, design, implementation, testing, and maintenance. It is inflexible to change.
- Iterative models allow repetition of phases to incrementally develop software. The incremental model delivers functionality in increments.
- Evolutionary models like prototyping and spiral development use iterative evaluation and refinement of prototypes to evolve requirements and manage risk.
- Other models include component-based development, formal methods, aspect-oriented development, and the Unified Process with iterative development of use cases. Personal and team software processes focus on self-directed teams, planning, metrics, and process improvement.
The document discusses software engineering and introduces some key concepts:
- Software engineering applies an engineering approach to software development by systematically collecting past programming experience.
- Following a defined software development life cycle model is important for developing software systematically and managing projects involving multiple engineers.
- Common life cycle models include waterfall, iterative waterfall, evolutionary prototyping, and spiral models. Adhering to a model helps track progress and avoid issues like the "99% complete" syndrome.
Integrating agile into sdlc presentation pmi v2pmimkecomm
The document discusses integrating Agile practices into a company's software development lifecycle (SDLC). It outlines key Agile concepts like product backlogs, sprints, and daily standups. It provides examples of how sprints can align with the SDLC and what deliverables each sprint produces. Critical success factors and potential adoption risks are also covered.
This document discusses software project management. It begins by defining what constitutes a project and size categories of software projects from trivial to extremely large. It then addresses that while software projects are similar to other projects, the invisibility of progress, complexity, and flexibility of software make them more difficult to manage. In the 1990s, analyses found that only 10% of software projects were delivered on time and budget, with management discipline being more important than technology. The document goes on to discuss activities covered by project management and introduces the waterfall model for examining software project frameworks both in theory and in practice.
The document discusses NASA's software engineering processes and requirements. It provides an overview of 12 key software engineering processes, including requirements management, planning and monitoring, measurement and analysis, software assurance, verification, configuration management, product integration, and their benefits. It also indicates which roles are typically involved with each process.
The document discusses various software process life cycle models, including:
- Waterfall model which progresses in linear stages from requirements to maintenance. It values predictability but is inflexible to changes.
- Prototyping model which adds prototyping stages to explore risks before full development.
- V model which mirrors each development phase with a testing phase. It emphasizes verification and validation.
- Iterative and incremental models like RUP which develop software iteratively in phases and increments, releasing early and often. This is more flexible and reduces risks compared to waterfall.
- Agile methods are also iterative and incremental but emphasize lightweight processes, adaptation, and flexibility over heavy documentation.
The
The document discusses software architecture reviews. It defines an architecture review as an activity to assess an architecture against review objectives. The goal is to uncover errors in design and ensure technical requirements are met. Effective reviews evaluate how architectural decisions impact requirements. The document outlines review inputs, techniques, and outcomes. It also discusses costs and benefits of reviews. Techniques include scenario analysis and checking for alternative designs. Benefits include early problem detection and improved architecture.
This document provides an overview of software engineering concepts including:
- The 4 P's of software development which are people, process, project, and product.
- Common software process models like waterfall, prototype, spiral, and RAD.
- Software engineering tasks like documentation, coding, implementation, and maintenance.
- Risks in software development such as technical risks, business risks, and customer risks.
The document discusses software process models which define a structured set of activities for developing software systems. These activities typically include specification, design & implementation, validation, and evolution. Process models provide organization and stability to software development. They define the approach taken and include activities like communication, planning, modeling, construction, and deployment. Process models can have different flows like linear, iterative, or evolutionary and can address problems at different levels of abstraction through patterns. Process assessment methods help ensure processes meet criteria for successful software engineering.
IASA is a non-profit professional association run by architects for all IT architects. It is centrally governed but locally run, technology and vendor agnostic. The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited.
The document discusses several software process models:
- The Linear Sequential (Waterfall) Model is a simple, systematic approach where each phase must be completed before moving to the next. It is best for small, well-defined projects.
- The Incremental Model applies the Linear Sequential Model iteratively to increments, delivering working software in stages. This allows for early delivery and flexibility.
- The Prototyping Model involves building prototypes to refine requirements through client feedback in iterations. This helps establish clear objectives.
- Rapid Application Development (RAD) is a fast version of the Linear Sequential Model using a component-based approach to accelerate delivery of fully functional projects.
This document covers key topics in software project management including scheduling, work breakdown structures (WBS), estimation, and network diagrams. It discusses estimating techniques like bottom-up and top-down, as well as analogy and expert judgment. Critical path method (CPM) and program evaluation review technique (PERT) network diagrams are explained for determining project schedules. The importance of realistic estimates to avoid project failure is emphasized. Brooks' law about the ineffectiveness of adding people to late projects is also referenced.
Requirements engineering process in software engineeringPreeti Mishra
Requirement Engineering (RE) involves understanding what customers want through tasks like elicitation, negotiation, and specification. RE helps establish requirements that provide a solid foundation for design and construction. The key RE tasks are inception to understand the problem, elicitation by drawing out requirements, elaboration by creating analysis models, negotiation to agree on a realistic solution, specification to formally describe requirements, validation to check for errors or issues, and management of changing requirements. RE helps software engineers better understand problems to solve through participation with customers, managers, and end users.
Project managers can improve project outcomes by (1) shaping projects around business architecture, (2) ensuring traceability from early lifecycle stages, and (3) conducting impact analysis to support business agility. This allows making quality, schedule, and results more predictable.
Technical Webinar: By the (Play) Book: The Agile Practice at OutSystemsOutSystems
In 2001, the Agile Manifesto took the world by storm, and it changed how software is built forever. Also in 2001, OutSystems, another disruptive force in the world of traditional waterfall software development, was born.
Not coincidentally, OutSystems has been using Agile Practices all along. However, because of the sheer speed at which we’re able to respond, we’ve had to come up with a few twists in our approach. We’re even putting it into a services delivery playbook.
In our webinar, “By the (Play)Book: The Agile Practice at OutSystems,” Engagement Guild Master and Expert Nuno Fernandes will show you how OutSystems approaches Agile Development and makes sure nothing slips.
In this session you will:
- Learn roles and respective responsibilities.
- Understand project phases with a clear focus on sprint development.
- Discover how we approach the user story life cycle in particular.
- See how a really solid structure, calendar and organization help maximize productivity.
Webinar: https://www.outsystems.com/learn/courses/59/webinar-the-agile-practice-at-outsystems/
Free Online training: https://www.outsystems.com/learn/courses/
Follow us on Twitter http://www.twitter.com/OutSystemsDev
Like us on Facebook http://www.Facebook.com/OutSystemsDev
Cisco Systems Case Study: The Architecture Review Process Improving the IT P...Susan Bouchard
Cisco Systems uses an Architecture Review Process (ARP) to evaluate and improve IT investments. The goal is to reduce duplication, increase productivity and deliver value. Key aspects of the ARP include engaging the Partner Architecture Team early in projects to provide technical expertise throughout the lifecycle. Documentation of architecture decisions is improved by providing a common format. Metrics are used to measure impacts such as redundancy eliminated and standards leveraged. Challenges include resource commitment, documentation quality and technology evolution. The action plan focuses on engagement, documentation, metrics and adoption.
The document discusses assessing maturity models PMI/OPM3 and CMMI within the context of the COBIT framework. It provides an agenda for an assessment including analyzing the approaches, identifying gaps, and recommending next steps. It describes the models and compares them, noting that while CMMI focuses on software engineering, OPM3 focuses on project management. The approach outlined analyzes the models' coverage within COBIT domains, assesses gaps, and recommends quantified next steps for gap closure.
Business Analyst Requirements Management Mark Borowski
The document discusses the importance of requirements management for business analysts and agile development. It addresses common myths about agile not needing formal requirements. Effective requirements definition includes types, abstraction levels, and best practices like traceability. Stories are discussed as a form of agile requirements but often need further elaboration. Requirements still matter in agile and need to be well-structured, organized, and linked to other artifacts to ensure quality and manage changes.
Process for requirement identification & development in software developmentRohana K Amarakoon
In this presentation, I explain about the best full process of requirement identification to final software delivery through following steps
1. Requirement identification
2. Elaboration of requirement
3. Requirement prioritisation
4. Agile software development
This document discusses various process models for software engineering:
- The waterfall model defines sequential phases of requirements, design, implementation, testing, and maintenance. It is inflexible to change.
- Iterative models allow repetition of phases to incrementally develop software. The incremental model delivers functionality in increments.
- Evolutionary models like prototyping and spiral development use iterative evaluation and refinement of prototypes to evolve requirements and manage risk.
- Other models include component-based development, formal methods, aspect-oriented development, and the Unified Process with iterative development of use cases. Personal and team software processes focus on self-directed teams, planning, metrics, and process improvement.
The document discusses software engineering and introduces some key concepts:
- Software engineering applies an engineering approach to software development by systematically collecting past programming experience.
- Following a defined software development life cycle model is important for developing software systematically and managing projects involving multiple engineers.
- Common life cycle models include waterfall, iterative waterfall, evolutionary prototyping, and spiral models. Adhering to a model helps track progress and avoid issues like the "99% complete" syndrome.
Integrating agile into sdlc presentation pmi v2pmimkecomm
The document discusses integrating Agile practices into a company's software development lifecycle (SDLC). It outlines key Agile concepts like product backlogs, sprints, and daily standups. It provides examples of how sprints can align with the SDLC and what deliverables each sprint produces. Critical success factors and potential adoption risks are also covered.
This document discusses software project management. It begins by defining what constitutes a project and size categories of software projects from trivial to extremely large. It then addresses that while software projects are similar to other projects, the invisibility of progress, complexity, and flexibility of software make them more difficult to manage. In the 1990s, analyses found that only 10% of software projects were delivered on time and budget, with management discipline being more important than technology. The document goes on to discuss activities covered by project management and introduces the waterfall model for examining software project frameworks both in theory and in practice.
The document discusses NASA's software engineering processes and requirements. It provides an overview of 12 key software engineering processes, including requirements management, planning and monitoring, measurement and analysis, software assurance, verification, configuration management, product integration, and their benefits. It also indicates which roles are typically involved with each process.
The document discusses various software process life cycle models, including:
- Waterfall model which progresses in linear stages from requirements to maintenance. It values predictability but is inflexible to changes.
- Prototyping model which adds prototyping stages to explore risks before full development.
- V model which mirrors each development phase with a testing phase. It emphasizes verification and validation.
- Iterative and incremental models like RUP which develop software iteratively in phases and increments, releasing early and often. This is more flexible and reduces risks compared to waterfall.
- Agile methods are also iterative and incremental but emphasize lightweight processes, adaptation, and flexibility over heavy documentation.
The
The document discusses software architecture reviews. It defines an architecture review as an activity to assess an architecture against review objectives. The goal is to uncover errors in design and ensure technical requirements are met. Effective reviews evaluate how architectural decisions impact requirements. The document outlines review inputs, techniques, and outcomes. It also discusses costs and benefits of reviews. Techniques include scenario analysis and checking for alternative designs. Benefits include early problem detection and improved architecture.
This document provides an overview of software engineering concepts including:
- The 4 P's of software development which are people, process, project, and product.
- Common software process models like waterfall, prototype, spiral, and RAD.
- Software engineering tasks like documentation, coding, implementation, and maintenance.
- Risks in software development such as technical risks, business risks, and customer risks.
The document discusses software process models which define a structured set of activities for developing software systems. These activities typically include specification, design & implementation, validation, and evolution. Process models provide organization and stability to software development. They define the approach taken and include activities like communication, planning, modeling, construction, and deployment. Process models can have different flows like linear, iterative, or evolutionary and can address problems at different levels of abstraction through patterns. Process assessment methods help ensure processes meet criteria for successful software engineering.
IASA is a non-profit professional association run by architects for all IT architects. It is centrally governed but locally run, technology and vendor agnostic. The use, disclosure, reproduction, modification, transfer, or transmittal of this work without the written permission of IASA is strictly prohibited.
The document discusses several software process models:
- The Linear Sequential (Waterfall) Model is a simple, systematic approach where each phase must be completed before moving to the next. It is best for small, well-defined projects.
- The Incremental Model applies the Linear Sequential Model iteratively to increments, delivering working software in stages. This allows for early delivery and flexibility.
- The Prototyping Model involves building prototypes to refine requirements through client feedback in iterations. This helps establish clear objectives.
- Rapid Application Development (RAD) is a fast version of the Linear Sequential Model using a component-based approach to accelerate delivery of fully functional projects.
This document covers key topics in software project management including scheduling, work breakdown structures (WBS), estimation, and network diagrams. It discusses estimating techniques like bottom-up and top-down, as well as analogy and expert judgment. Critical path method (CPM) and program evaluation review technique (PERT) network diagrams are explained for determining project schedules. The importance of realistic estimates to avoid project failure is emphasized. Brooks' law about the ineffectiveness of adding people to late projects is also referenced.
Requirements engineering process in software engineeringPreeti Mishra
Requirement Engineering (RE) involves understanding what customers want through tasks like elicitation, negotiation, and specification. RE helps establish requirements that provide a solid foundation for design and construction. The key RE tasks are inception to understand the problem, elicitation by drawing out requirements, elaboration by creating analysis models, negotiation to agree on a realistic solution, specification to formally describe requirements, validation to check for errors or issues, and management of changing requirements. RE helps software engineers better understand problems to solve through participation with customers, managers, and end users.
Project managers can improve project outcomes by (1) shaping projects around business architecture, (2) ensuring traceability from early lifecycle stages, and (3) conducting impact analysis to support business agility. This allows making quality, schedule, and results more predictable.
Technical Webinar: By the (Play) Book: The Agile Practice at OutSystemsOutSystems
In 2001, the Agile Manifesto took the world by storm, and it changed how software is built forever. Also in 2001, OutSystems, another disruptive force in the world of traditional waterfall software development, was born.
Not coincidentally, OutSystems has been using Agile Practices all along. However, because of the sheer speed at which we’re able to respond, we’ve had to come up with a few twists in our approach. We’re even putting it into a services delivery playbook.
In our webinar, “By the (Play)Book: The Agile Practice at OutSystems,” Engagement Guild Master and Expert Nuno Fernandes will show you how OutSystems approaches Agile Development and makes sure nothing slips.
In this session you will:
- Learn roles and respective responsibilities.
- Understand project phases with a clear focus on sprint development.
- Discover how we approach the user story life cycle in particular.
- See how a really solid structure, calendar and organization help maximize productivity.
Webinar: https://www.outsystems.com/learn/courses/59/webinar-the-agile-practice-at-outsystems/
Free Online training: https://www.outsystems.com/learn/courses/
Follow us on Twitter http://www.twitter.com/OutSystemsDev
Like us on Facebook http://www.Facebook.com/OutSystemsDev
Cisco Systems Case Study: The Architecture Review Process Improving the IT P...Susan Bouchard
Cisco Systems uses an Architecture Review Process (ARP) to evaluate and improve IT investments. The goal is to reduce duplication, increase productivity and deliver value. Key aspects of the ARP include engaging the Partner Architecture Team early in projects to provide technical expertise throughout the lifecycle. Documentation of architecture decisions is improved by providing a common format. Metrics are used to measure impacts such as redundancy eliminated and standards leveraged. Challenges include resource commitment, documentation quality and technology evolution. The action plan focuses on engagement, documentation, metrics and adoption.
This document provides a summary of SriHarshaKota's professional experience as a QA Analyst/Test Lead with over 7.5 years of experience in testing for the banking, telecom and project management domains. He has extensive experience with tools like QTP, ALM and databases like Oracle and SQL Server. Some of his responsibilities include test automation, test planning, defect tracking, database testing and mentoring junior team members. He is proficient in Agile methodologies and has worked on projects for clients like Scotia Bank, Unilever and Telstra.
The document provides information about Luiz Barboza, including his education background and certifications. It then outlines the agenda for a course on performance evaluation of information systems, covering topics like workload modeling, performance requirements, tools for performance analysis and testing, and performance modeling.
Sreedhar Bandaru is a senior test lead with over 11 years of experience in software testing and development. He has expertise in performance testing, test automation, and testing various technologies including telecom protocols and PBX systems. Currently he is a technical test lead for a Microsoft project, where he is responsible for test planning, requirements gathering, test automation, and client communication.
Lakshmi Chaitanya Arikela has over 4 years of experience as a Technical Specialist developing and implementing ERP systems using Progress 4GL. She currently works as a Technical Lead for Visteon Corporation, where she is responsible for requirement gathering, development, testing, and delivering projects like Business Access Control on time and within budget. Prior to this, she has worked on projects for clients such as Rockwell Automation and Thermasys Corporation developing modules for their MFG/PRO systems.
The document summarizes Emporia State University's upgrade of their Banner system from version 8.0 to 8.1. It discusses project planning, scope, business process analysis and testing. The upgrade project took 8 months and involved upgrading various modules including Student, Finance, HR and Advancement to Banner 8.1. It also included upgrading supporting software, hardware infrastructure, and addressing issues encountered during testing and integration. Lessons learned focused on importance of collaboration between functional and technical teams for a successful major release upgrade.
Bhanu Prasad is a data engineer with 9 years of experience working with tools like Teradata, Informatica, and DataStage. He has expertise in ETL development, testing, and support. His experience includes projects in banking, e-commerce, retail, and telecommunications. Currently he works as a senior Teradata consultant for OCBC Bank in Singapore.
Read Curriculum vitae of Shwetabh Kumar as Project Manager at Deloitteshwetabhkumar
Hello, My name is Shwetabh Kumar and I am from Hyderabad. Presently I am associated with Deloitte Company as a Project Manager. Skilled in designing and developing modules/products, managing and tracking project execution, executing test scenarios, releasing products to production.
This professional profile summarizes Sandeep Pawar's experience as a Project Manager with over 12 years of experience in software development and project management. He has managed teams of 5-17 resources on varied technology projects, and has skills in Agile, Waterfall, and Six Sigma methodologies. He is a certified PMP, Scrum Master, and Six Sigma Green Belt with a track record of delivering projects on time and within budget.
Resume of Shwetabh Kumar, Project Manager at Deloitteshwetabhkumar
My name is Shwetabh Kumar and I am presently associated with Deloitte as a Project Manager/Application Designer in Hyderabad. Possess good interpersonal, analytical and team building skills with ability to establish quality systems.
The document outlines the experience and qualifications of an IT professional, including over 18 years of experience managing large projects over $7M for clients in various industries. They have a track record of delivering complex applications on time and on budget using technologies like .NET, SQL Server, and Oracle. Their roles have included project management, team leadership, software development, and ensuring quality and compliance on various projects.
This presentation focuses on the basics of Performance Engineering and touches upon relevant aspects of SPE or Systems Performance Engineering across the development, implementation and support cycle.
This document discusses project planning, feasibility studies, and various factors to consider for IT projects. It covers guidelines for project plans, internal and external factors, components of a project plan, the project development lifecycle including planning, analysis, design, implementation, and support phases. It also discusses assessing the feasibility of projects, including tests of operational, technical, schedule, and economic feasibility. Methods for evaluating feasibility include feasibility matrices and analyses of benefits, costs, payback periods, and net present values. Managing stakeholder expectations is also addressed.
• Seasoned data engineer with 9 years of experience in data warehousing business intelligence. Hands on experience in large scale, Massively Parallel Processing, distributed and highly available database systems. Having exposure on various domains like Banking, E-Commerce/Online payments, medical systems, Fashion Application Systems (FAS), Retailer, telecom industry and Logistics.
This document contains the resume of Satyanarayan K Adi. He has over 14 years of experience as a Technical Project Manager working with technologies like .NET and Oracle. He holds a Master's degree in Computer Applications and Bachelor's degree in Science. Some of his key skills and responsibilities include resource management, quality management, requirement gathering, estimating, planning, tracking, and risk management. He has experience managing projects in various domains for clients such as Jindal Rolling Mill, IATA, and Nabors Corporate Services.
This document outlines the main responsibilities of different team members on a project. It describes the roles of a project manager, developers, and QA. It also includes sections on project definition, workflow, and an escalation matrix. The project manager leads projects from start to finish, tracks progress, assigns resources, and ensures quality standards. Developers are responsible for coding, testing, and validating technical solutions. QA defines test plans, checks compliance, and performs testing.
Sandeep Gupta is a Product Specialist at Subex Ltd in Bangalore, India with over 3.8 years of experience in software development. He has a Bachelor's degree in Computer Science and seeks challenging roles in software project management, implementation, and support. His skills include Java, Oracle, shell scripting, and he has experience in software development lifecycles, requirements analysis, and testing. He currently handles tier 2 customer support, trains clients, and fine tunes revenue assurance products.
Similar to How Meark as an enterprise leverages DSDM? (20)
ANIn Coimbatore April 2023 | Lean,Agile & DevOps-How applied together provide...AgileNetwork
Agile Network India - Coimbatore
Title: Lean,Agile & DevOps-How applied together provides the best outcomes by Shanmuganand Sivaraman
Date: 22nd April 2023
Hosted by : Kovai
ANIn Ahmedabad June 2024 | Business outcomes directly proportional to mindset...AgileNetwork
Agile Network India - Ahmedabad
Title: Business outcomes directly proportional to mindset by Bhumi Goklani
Date: 01st June 2024
Hosted by :Solution Analysts Pvt.Ltd
ANIn Coimbatore May 2024 | Being Agile - Fortifying the GenZ Workforce by Sar...AgileNetwork
Agile Network India -Coimbatore
Title: Being Agile - Fortifying the GenZ Workforce by Sarada Jayaraman
Date: 25th May 2024
Hosted by : PSGR Krishnammal College for Women
ANIn Coimbatore May 2024 | Skills for the Evolving IT landscape by Meena Subr...AgileNetwork
Agile Network India- Coimbatore
Title: Skills for the Evolving IT landscape by Meena Subramaniam
Date: 25th May 2024
Hosted by : PSGR Krishnammal College for Women
ANIn Ahmedabad Jan 2023 | Discovery is not a phase in being Agile its, "The A...AgileNetwork
Agile Network India - Ahmedabad
Title: Discovery is not a phase in being Agile its, "The Approach" by Vishal Jariwal
Date: 28th Jan 2023
Hosted by: Third Rock Techno LLP
ANIn Ahmedabad April 2023 | Importance of agile and how it can be Implemented...AgileNetwork
Agile Network India - Ahmedabad
Title: Importance of agile and how it can be Implemented in real world by Tanmay Panchal
Date: 22nd April2024
Hosted by: 7 Span
ANIn Chennai May 2023 | Navigating the Rapids: Embracing Agility to Conquer E...AgileNetwork
Agile Network India - Chennai
Title: Navigating the Rapids: Embracing Agility to Conquer Everyday Project Challenges by Andrews Roberta Mary R
Date: 18th May 2024
Hosted by: Truckrr Information Services Pvt Ltd
ANIn Navi Mumbai Jan 2023 | Agile project development -"A Journey" by Indulek...AgileNetwork
Agile Network India - Navi Mumbai
Title: Agile project development -"A Journey" by Indulekha sing
Date: 28th Jan 2024
Hosted by: Merce Technologies Pvt Ltd
ANIn Ahmedabad May 2024 | Sailing the Agile seas Leveraging Business Prioriti...AgileNetwork
Agile Network India : Ahmedabad
Title: Sailing the Agile seas Leveraging Business Priorities and Estimation by Nirav Sanghavi
Date: 04th May 2024
Hosted by: Oneclick IT Consultancy PVT Ltd
ANIn Chennai April 2024 |Agile Engineering: Modernizing Legacy Systems by Ana...AgileNetwork
Agile Network India - Chennai
Title: Agile Engineering: Modernizing Legacy Systems by Ananth Venugopal
Date: 27th April 2024
Hosted by: ClearVue Solutions Pvt. Ltd
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
1. Presented by
Meark Enterprise Private Limited
Consulting, IT Products and Services organization
established in Feb 2016.
ISO 9001 (Quality) and ISO 27001 (Information Security)
certified organization
Meark’s Vision
To provide significant value to our clients by
architecting optimized processes and systems
for efficient business functioning.
Sectors
Agriculture
Education and Skilling
Public sector
Retail
Banking
Insurance
Healthcare
Manufacturing
Our Focus
Solutions devoted to users not technologies.
2. Nithya Subramaniam
Managing Director
Meark Enterprise Private Limited
How Meark as an Enterprise Leverages DSDM?
Nithya has more than 16 years of experience and is a recognized expert in the software
business analysis and architecture field .
She currently leads the Exploration and Engineering teams of Meark to deliver Consulting, IT
Services and Products enabling clients to do business better by technology and process
changes.
Her earlier roles include
Consultant and Senior Manager for Innovations, Campus Management Corp.
Product Manager, NEC India
Practice manager for Higher Education Sector , Wipro
Multiple business analysis engagements in the retail sector, Wipro
7. Presented by
Why DSDM Framework?
Start-up
Model to follow
One ofAgile
And a proven model
Gain Compliance
For ISO and CMMI Standards
Easy to Communicate
Less documentation
Focus on Output
DSDM
(1994)
Iterative and Incremental
To provide more discipline to the
rapid application development .
IT and Non-IT Projects
Agile Manifesto
(2001)
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
8. Presented by
What is Dynamic Systems Development Method(DSDM)
Focus on the business need
Deliver on time
Collaborate
Never compromise quality
Build incrementally from firm foundations
Develop iteratively
Communicate continuously and clearly
Demonstrate control
Principles
Prioritisation Technique – MoSCoW
Must Have
60%
Should Have
20%
Could Have
20 %
Won’t Have
Timebox Plan
Iterative 4 Week
Sprints
Terms of
Reference
Benefit Assessment
8
6
Phases
14. Presented by
Better Visibility
Missed components and priorities due to
definition misses.
[ One board]
Missed components and priorities due to
definition misses.
[ One board]
Better visibility for planning.
[Two boards – Exploration and Engineering]
Better visibility for planning.
[Two boards – Exploration and Engineering]
PC
Project Co-ordinator Before
Before After
After
17. Presented by
DSDM - Prioritisation Technique
Prioritisation Technique – MoSCoW
Must Have
- 60%
Should
have - 20%
Could have
- 20 %
Won’t
have
18. Presented by
Freedom to Choose within the boundary
Project Co-ordinator
1. Team’s identify component’s to built
1. Team’s identify component’s to built
1. Mark identified sprint components they
choose to do for the day
1. Mark identified sprint components they
choose to do for the day
Before
Before After
After
20. Meark – Exploration Sprint
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story(PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoW,
Timeboxplan*
PC, PA EmailTA,
Developer,TL
SRS Document SAT PA
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Buglist SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
DeliveryPlan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Legend
Reference for further reading: https://www.agilebusiness.org/
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 5.0
* represents Milestone
Products
SAT- Solution Analyst and Tester
UI-UI Developer
TL- Team Lead
DEV-Developer
PC- Project Co-ordinator
PA- Process Architect
TA- TechnicalArchitect
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary(PC)*
Deployment Phase
Week4
Week2,3
Code Review per
component by
TL/Dev
Weekly Code
Optimization by
TA
Post - Project Phase Benefits Assessment
DSDM Evolutionary Products (Optional)
Week4
Week 2,3
Evolutionary Development Phase - Exploration + Engineering
Draft
Refinement
Optimization
Exploration States
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story (PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoWComponent
List , Timeboxplan*
PC, PA, TA TL, SAT Validations,
Notiifcations, SRS
Document
SAT PA
Week 2,3
Evolutionary Development Phase - Exploration + Engineering
23. Presented by
Structured Reviews, Yet in any Order!
1. UI multiple-changes as Issue
2. Developers work on changing UI
1. UI multiple-changes as Issue
2. Developers work on changing UI
1. UI in Exploration Sprint
2. 3 level UI reviews yield best possible
design
3. Validations upfront
1. UI in Exploration Sprint
2. 3 level UI reviews yield best possible
design
3. Validations upfront
Before
Before After
After
PA
SAT
UI
24. Meark – Engineering Sprint
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story(PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoW,
Timeboxplan*
PC, PA EmailTA,
Developer,TL
SRS Document SAT PA
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Buglist SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
DeliveryPlan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Legend
Reference for further reading: https://www.agilebusiness.org/
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 5.0
* represents Milestone
Products
SAT- Solution Analyst and Tester
UI-UI Developer
TL- Team Lead
DEV-Developer
PC- Project Co-ordinator
PA- Process Architect
TA- TechnicalArchitect
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary(PC)*
Deployment Phase
Week4
Week2,3
Code Review per
component by
TL/Dev
Weekly Code
Optimization by
TA
Post - Project Phase Benefits Assessment
DSDM Evolutionary Products (Optional)
Week4
Week 2,3
Evolutionary Development Phase - Exploration + Engineering
Code
Review
Release
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week 1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Bug list SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Week 4
Week 2,3
Code Reviewper
component by
TL/Dev
Weekly Code
Optimization by
TA
Engineering States
25. Presented by
Structured Reviews, Yet in any Order!
1. Daily Dependency on Architect in
Development
1. Daily Dependency on Architect in
Development
Only reviews and logic complexity requires
intervention of technical architect.
Only reviews and logic complexity requires
intervention of technical architect.
Before
Before After
After
TA
TL, DEV
26. Presented by
Meark -Sample Monthly Sprint Planner and Tracker
Sprint Items Responsible Duratio
n
in Hrs
Planned
Work
Dates
Responsible
Person
Completion
Status
Overall
Status
Tester
Confirmatio
n
Technical
Review
and
Dependency
Functional
Review
and
Dependency
Organization Registration Public Page -
Resolving Duplicate Registration Issue CR -
SCR -USR- ORS-014
Dev A 4 7 Completed Completed Completed NA Completed
Manage GST and Fee – SCR -USR- ORS-012 Dev A 6 7 Completed Open Completed Completed Completed
Manage Subscription – SCR-VMS–SUB -002
Dev B
24
Open Open Completed Completed Completed
View Subscription Packs – Public page -
SCR-VMS–SUB -002 Dev A 24 15,22,29
Completed Open Completed Completed Completed
Payment Registration and Integration for
Sports 2.
with Receipt Generation Dev C 8 8,15,22,1
Open Open
Pending Completed Completed
Website update – Inclusion of New content
page SCR-WES–POR -034 Dev C 4 22 Completed Completed NA NA Completed
Available duration for Sprint
in hours starting 1st Dec
160
29. Presented by
Meark – Performance - Sample View of a Month
SN Key Performance
Areas (KPA)
Key Performance Indicator (KPI) Max
Score
Associate
Score
Associate
Score
Associate
Score
Associate
Score
Associate
Score
Sprint PerformanceProject Team Performance as determined by Quality of Sprint Deliverables
or Opportunities created/capitalized.
50 30 49.5 30 42 49.5
1Deliver on Time 1a. Focus on business priorities. Guarantee Minimum Usable Subset.
1b.Always hit deadlines. Ability to stretch when work is incomplete/ required for business by self or as requested.
2a. For Dev and SAT: Occurrences of missing requirements as identified in testing/review. Pro-active scheduling of
Review/UAT with Manger/customer and ensuring sign-off.
Zero delays.
10 6 10 5 9 10
2Never Compromise
Quality
1. Adherence to provided formats for Email Signature, Release emails.
For Developer: Code Conventions, Quality of code as identified in review by TL/TA.
For SAT : Quality of requirement and test document with coverage of scenarios, as reviewed by PA/PM/Client.
2. For Developer: Defects/unresolved issue re-opened by tester and manager.
For SAT: Defect identified by manger/customer post system release.
10 8 10 8 8 9.5
3Embrace Change,
Experiment and
Learn
1a. Instances of Exploration and Implementation of new UI pattern/Technology component/ New Applications/
Application Improvements.
1b. Accept change positively and handle changing workloads in response to changing circumstances.
2a. Learning sessions participated at least 6 hrs.
2b. Learning conducted/showcased at least 1, min of 30 mins. Willingness to learn new skills, attend self-improvement
training.
10 5 9.5 6 8 10
4Collaborate,
Communicate
Continuously
and Clearly
1a. Participation is delayed/absent in meetings/ Sprint sessions.
1b. Pro-active scheduling of required reviews/meetings. Pro-active transparent communication of a) change in time, in
case of delay, b) change in task from what is planned on daily/given task. Number of times follow-up email where
received.
2a. Daily update in Kanban and email without follow-up. Appropriate Response for query post in email within 30 mins
during work hours. Clear and independent communication without grammatical errors. When Associate/Manager is not
available for immediate clarification for doubt, has mail been sent out immediately.
For SAT includes: Presence in project kick-off call with TA.
2b. Early communication of leave request, permission requirement. Maximum of 2 permission per month.
10 7 10 7 8 10
5Initiatives Initiatives as recognized by the Manager 10 8 10 8 9 10
Total 100 64 99 64 84 99
30. Presented by
Team Performance Ratings – In Sprint too!
1. 6 months feedback meetings on 10
competencies
2. Yearly appraisals
1. 6 months feedback meetings on 10
competencies
2. Yearly appraisals
1. Monthly Feedback Emails and Awards
2. Rated based on 5 points by PA/TA
3. Yearly appraisals
1. Monthly Feedback Emails and Awards
2. Rated based on 5 points by PA/TA
3. Yearly appraisals
Before
Before After
After
Team
32. Presented by
DSDM – Detailed in 2 Pages
Our workplan
and output for
each week of the
month sprint and
increment
RACI Matrix
For each output
Responsible, Accountable,
Consulted, Informed
33. Output Responsible Reviewer Output Responsible Reviewer
Wireframes SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA,Email
TA
DB Review TL/TA PA
MoSCoW,
Timeboxplan*
SAT,PA EmailTA,
Developer,TL
_ _ _
Sprint In Output Responsible Reviewer Output Responsible Reviewer
Week 1 Code with UI DEV, TL SRS Document SAT PA
Code with
SRS Document
DEV, TL Prepare Test cases
and Test Data
SAT PA
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Bug list SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
Delivery Plan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Evolutionary Development Phase
User Interface
Post - Project Phase Benefits Assessment*
DSDM Evolutionary Products (Optional)
Week 4
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 4.0
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary (PC)*
Deployment Phase
Week 4
Week 2,3
Code Reviewper
component by
TL/Dev
Weekly Code
Database
SN DSDM Phase Project Activities PC PA TA SAT UI TL/DEV
1 Pre-Project Phase Terms of Reference* I RA C I - -
2 Feasibility Phase Feasibility Assessment (PC)* RA C C C - -
3 Foundation Summary Foundation Summary (PC)* RA RA C C - -
4 Foundation Summary Provide Functional requirements I RA I C - -
5 Foundation Summary Delivery Plan RA C C C - -
6 Evolutionary Development Phase UI - Wireframes I A C R - -
7 Evolutionary Development Phase UI - Draft I I I AC R -
8 Evolutionary Development Phase UI- Refinement I C C AC R -
9 Evolutionary Development Phase UI - Optimization I C C AC R -
10 Evolutionary Development Phase DB Design I C RA C - -
11 Evolutionary Development Phase DB Review I C RA C - -
12 Evolutionary Development Phase Provide Component IDs (Screens/Reports/APIs) I C I RA - -
13 Evolutionary Development Phase SRS Document I C I RA - -
14 Evolutionary Development Phase Review SRS I RA I C - -
15 Evolutionary Development Phase Write SRS Requirements with DB Table names I I C RA - -
16 Evolutionary Development Phase Write Scripting in Json templates (if required) I I C RA - I
17 Evolutionary Development Phase Identify TL/DEV, Plan Sprint,MoSCoW,Timebox plan* RA C C C I I
18 Evolutionary Development Phase Team Specific Sprint Meetings and daily progress update RA C C C I I
19 Evolutionary Development Phase Provide KT to Developer I C I RA - I
20 Evolutionary Development Phase Dev Kickoff call I - RA C - C
21 Evolutionary Development Phase Prepare Test cases and Test Data I C I RA - -
22 Evolutionary Development Phase Code with UI I C C C C RA
23 Evolutionary Development Phase Code with SRS Document and Unit Test I C C C C RA
24 Evolutionary Development Phase Provide Functional clarification to developers I C C RA C I
25 Evolutionary Development Phase Provide Technical clarification to developers I - RA C C C
26 Evolutionary Development Phase Review development progress in Daily Sprint calls RA I I C - C
27 Evolutionary Development Phase Release Multiple Cycles - Release Email I I C I - RA
28 Evolutionary Development Phase Test Multiple Cycles -Smoke Test Accept/Reject, Daily Bug list I I I RA - C
29 Evolutionary Development Phase End of Sprint - Retrospective Meeting, Next Sprint planning RA C C C C C
30 Evolutionary Development Phase Timebox Review Record* C C RA I I I
30 Deployment Phase Project Review Report* RA C I I I I
31 Deployment Phase Assemble Review Deploy to UAT I I C I - RA
32 Deployment Phase User Guide I C I RA - C
33 Deployment Phase Conduct UAT and get Sign-off I C I RA - -
34 Deployment Phase End User Training I C I RA - -
35 Deployment Phase Deploy to Prod I I C I - RA
36 Post - Project Phase Benefits Assessment* C RA I C - -
37 Any Phase- Evolutionary Products Business Case, Priortized Requirements List I RA C C - -
38 Any Phase- Evolutionary Products Delivery Plan, Management Approach Definition RA C C C - -
39 Any Phase- Evolutionary Products Solution Architecture Definition C A R I - -
40 Any Phase- Evolutionary Products Development Approach Definition C C RA I - -
Legend:
* represents Milestone products
Responsible Those who do the work to complete the task
Accountable One ultimately answerable for correctness and completion
Consulted Those whose opinions are sought
Informed Those who are kept up-to-date on progress
DSDM RACI Matrix
Version 4.0
RACI
37. Presented by
Meark Products
Visitark Stark Inspectark
Inspection Management
Spark
Devark
Sector
Specific
Sector
Agnostic
Skillar
Skill and Placements for
Skilling Sector
Agriark
Agriculture Produce
Aggregator
Visitor Management Guest Houses and Halls
Management
Alumni and Placement
for Education Sector
Event Management for
Education Sector
38. Presented by
Meark Services
Integration with
Enterprise and National
systems
Robotic Process
Automation
Reporting and Analytics
Mobile Apps in
Cordova / PWA
Website Development
Application Design &
Development
39. Our Clients and End Clients/ Users of Meark
Now Anthology
Talisma Corporation Pvt. Ltd
TNSDC
CET Maharashtra Directorate of
Technical Education,
Chhattisgarh
Development partners Indian Center for Social Transformation, Tech Mahindra.
Interfaces with IMD, ISRO, ICAR, DACFW, NWIC, CGWB
End users Farmers, Farm Suppliers and Buyers
40. Ability to see vehicles on the Maps with statuses and geocoding
Vehicle Tracking
RFID based Bin Tracking -
Pharmacy Distribution Company