The document discusses Microsoft SharePoint server farm topologies and sizing recommendations. It covers factors to consider like availability, capacity, performance, and organizational requirements. It provides guidance on the number of servers, databases, web applications, and other components for small, medium and large farm designs based on the number of users and workload. It also discusses virtualization support and recommendations.
This document discusses architecture governance based on the TOGAF framework. It defines governance as ensuring things are done according to guidelines and objectives. Architecture governance specifically manages enterprise architectures at the organizational level, providing services to facilitate innovation while adhering to guidelines. The TOGAF framework covers governance areas like compliance management. It identifies governance roles in the ADM phases and defines a meta model. COBIT can also be integrated to assess architecture compliance with corporate policies and strategies. Without governance, risks increase that solutions may not meet requirements.
Example of the stage-gate product management process (sometimes referred to as the phase-gate process). This type of process is used to bring new products or updates to market. At the completion of each phase, there is general a review of the project along with a go / no go / hold / rework decision.
Business analysis can involve many different roles beyond just being a link between IT and the business. A business analyst (BA) helps facilitate improvements across technology, processes, and people. They may work with various teams like marketing to provide estimates and solutions or be involved in requirements gathering once a project begins. BAs can also drive profits by improving processes. Importantly, BAs may specialize in particular business domains.
Thoughts on productivity in software developmentMichael Vax
This talks explores different aspects of productivity in developing software.
- What is productivity and how to measure it
- Productivity on multiple levels
- Individual
- Team
- Organization
Patterns & Anti-patterns
Microsoft PPM helps you deliver on business strategies through high-impact outcomes. You can think of the PPM as a lifecycle which comprises of three phases: Ideate, Plan, and Execute.
Ideate: Is the initiation phase in which ideas are collected and projects are proposed. The organization’s business drivers capture the company’s strategy and guide ideation.
Plan: This phase includes preliminary planning of the projects at a high level. Microsoft PPM helps prioritize the projects subject to budget and resourcing constraints. Once projects are approved the solution supports detailed and realistic planning.
Execute: The goal of this phase is to deliver the projects through collaboration of the involved stakeholders.
Built on Microsoft’s cloud Microsoft PPM weaves in cloud services that power the PPM solution with collaboration capabilities, advanced analytics that drive insights and the ability to customize and extend the solution to meet unique needs of your organization.
Microsoft PPM is built on Microsoft’s cloud infrastructure. This means you get enterprise-grade security and compliance, highly secure and geographically diverse data centers, and a 99.9% uptime guarantee.
Efficient Parallel Testing with Docker by Laura FrankDocker, Inc.
Fast and efficient software testing is easy with Docker. We often
use containers to maintain parity across development, testing, and production environments, but we can also use containerization to significantly reduce time needed for testing by spinning up multiple instances of fully isolated testing environments and executing tests in parallel. This strategy also helps you maximize the utilization of infrastructure resources. The enhanced toolset provided by Docker makes this process simple and unobtrusive, and you’ll see how Docker Engine, Registry, Machine, and Compose can work together to make your tests fast.
Managing and supporting PowerApps & Flow at scale by Daniel LaskewitzDaniel Laskewitz
The document discusses how to establish governance over a Power Platform environment. It recommends establishing an environment strategy, setting up data loss prevention policies, leveraging built-in activity logs and analytics, installing a Center of Excellence starter kit, welcoming new users and identifying champions, and establishing automated audit processes. The agenda covers product discovery, security layers, demoing DLP policies, monitoring activity, leveraging management tools, and nurturing an app catalog.
The document discusses Microsoft SharePoint server farm topologies and sizing recommendations. It covers factors to consider like availability, capacity, performance, and organizational requirements. It provides guidance on the number of servers, databases, web applications, and other components for small, medium and large farm designs based on the number of users and workload. It also discusses virtualization support and recommendations.
This document discusses architecture governance based on the TOGAF framework. It defines governance as ensuring things are done according to guidelines and objectives. Architecture governance specifically manages enterprise architectures at the organizational level, providing services to facilitate innovation while adhering to guidelines. The TOGAF framework covers governance areas like compliance management. It identifies governance roles in the ADM phases and defines a meta model. COBIT can also be integrated to assess architecture compliance with corporate policies and strategies. Without governance, risks increase that solutions may not meet requirements.
Example of the stage-gate product management process (sometimes referred to as the phase-gate process). This type of process is used to bring new products or updates to market. At the completion of each phase, there is general a review of the project along with a go / no go / hold / rework decision.
Business analysis can involve many different roles beyond just being a link between IT and the business. A business analyst (BA) helps facilitate improvements across technology, processes, and people. They may work with various teams like marketing to provide estimates and solutions or be involved in requirements gathering once a project begins. BAs can also drive profits by improving processes. Importantly, BAs may specialize in particular business domains.
Thoughts on productivity in software developmentMichael Vax
This talks explores different aspects of productivity in developing software.
- What is productivity and how to measure it
- Productivity on multiple levels
- Individual
- Team
- Organization
Patterns & Anti-patterns
Microsoft PPM helps you deliver on business strategies through high-impact outcomes. You can think of the PPM as a lifecycle which comprises of three phases: Ideate, Plan, and Execute.
Ideate: Is the initiation phase in which ideas are collected and projects are proposed. The organization’s business drivers capture the company’s strategy and guide ideation.
Plan: This phase includes preliminary planning of the projects at a high level. Microsoft PPM helps prioritize the projects subject to budget and resourcing constraints. Once projects are approved the solution supports detailed and realistic planning.
Execute: The goal of this phase is to deliver the projects through collaboration of the involved stakeholders.
Built on Microsoft’s cloud Microsoft PPM weaves in cloud services that power the PPM solution with collaboration capabilities, advanced analytics that drive insights and the ability to customize and extend the solution to meet unique needs of your organization.
Microsoft PPM is built on Microsoft’s cloud infrastructure. This means you get enterprise-grade security and compliance, highly secure and geographically diverse data centers, and a 99.9% uptime guarantee.
Efficient Parallel Testing with Docker by Laura FrankDocker, Inc.
Fast and efficient software testing is easy with Docker. We often
use containers to maintain parity across development, testing, and production environments, but we can also use containerization to significantly reduce time needed for testing by spinning up multiple instances of fully isolated testing environments and executing tests in parallel. This strategy also helps you maximize the utilization of infrastructure resources. The enhanced toolset provided by Docker makes this process simple and unobtrusive, and you’ll see how Docker Engine, Registry, Machine, and Compose can work together to make your tests fast.
Managing and supporting PowerApps & Flow at scale by Daniel LaskewitzDaniel Laskewitz
The document discusses how to establish governance over a Power Platform environment. It recommends establishing an environment strategy, setting up data loss prevention policies, leveraging built-in activity logs and analytics, installing a Center of Excellence starter kit, welcoming new users and identifying champions, and establishing automated audit processes. The agenda covers product discovery, security layers, demoing DLP policies, monitoring activity, leveraging management tools, and nurturing an app catalog.
This document provides an agenda for a release showcase meeting covering a software project. The agenda includes an overview of the project, its team members, sprint goals and backlog, velocity, a demonstration of work completed, and next steps. Attendees will learn about the project progress, deliverables for the current sprint, and have an opportunity to ask questions.
This document provides a checklist for business readiness planning with questions in several key areas: change strategy, communications, training, support, and documentation. It prompts identifying stakeholders and their roles, how the change supports organizational priorities, leading people through the change process, evaluating stakeholder buy-in, managing resistance, defining key messages and audiences, identifying training needs and timelines, planning support resources and evaluation, and determining documentation requirements. The checklist aims to guide comprehensive planning across multiple workstreams to successfully implement organizational changes.
This document lists and explains 17 important formulas used in project management and referenced in the PMBOK Guide. The formulas calculate things like number of communication channels on a team, schedule and cost performance indexes, variances, estimates, and float. Mastering these formulas is essential for solving calculation questions on the Project Management Professional (PMP) certification exam. Additional study materials are recommended if further guidance is needed on applying the formulas.
You can get this presentation template:
GraphicRiver:
PowerPoint http://bit.ly/2Yi4ybr
Apple Keynote http://bit.ly/2XVOKqp
Envato Elements:
PowerPoint http://bit.ly/2XWbyGy
Apple Keynote http://bit.ly/2XVDjyT
Project status report is a detailed report on project progress. Its purpose is to effectively and efficiently communicate project status at regular intervals to project stakeholders. Good, consistent, project status reporting helps guard against unexpected surprises to project stakeholders. It keeps project stakeholders informed of critical aspects of project health such as schedule, issues, product, resources, team, cost, expenses, value, solution, roadmap, etc.
CONTENT:
Agenda
Introduction
Project Details
Project Needs
Solution
Top Management
Management Team
Key Personnel
Project Team
Project Team Organization
Our Strengths
Awards
Project Phases
Year Project Phases
Project Phase Model
Road Map
Project Structure
Milestone Plan
Planning Chart
Product Creation Process
Tools and Technologies
Gantt chart – One Week
Gantt chart – One Month
Gantt chart – Three Month
Gantt chart – Six Month
Yearly Gantt Chart
Task Timeline
Meeting Schedule
Marketing Approach
Market Share
Market Trends
Positioning
Target Customer
Competitors Market Share
Competitive Advantage
Risk Analysis
Project Pros and Cons
Delays and Causes
Change Recommendations
Expenses
Projecting Profit and Loss Statement
Price Table
Price Plans
Image Gallery
Product
Project Closure Terms
Conclusion Table
Contacts
This document provides an interim report on developing a healthy community food system plan for Waterloo Region. It summarizes the current state of the local food system and its impacts on public health. Key points include:
1) The local food system influences the nutrition environment and public health in the region.
2) A review was conducted of local studies on agriculture, food availability, buying practices, and dietary intake.
3) Objectives and preliminary strategies are outlined to guide further planning, including ensuring affordable access to nutritious food, strengthening the local food economy, and forging partnerships to implement the plan.
The document provides a project charter and plan for upgrading Middlesex School's Sage Millennium fundraising software from version 7.7 to 7.9 Service Pack 2. The project has 7 phases: 1) planning, 2) analyzing the current system, 3) implementing and testing a new system, 4) reviewing new functionality, 5) training users, 6) going live with the new system, and 7) optimizing post go-live. The project aims to have the new system online by the end of the fiscal year on July 15, 2012.
Qualidade de Software e normas ISO 15504, 12207, MPS.BR e Empresa CertificadaVinicius_Nunes
O documento resume as normas ISO 15504 (SPICE), ISO 12207 e MPS.BR para avaliação e melhoria de processos de software. A ISO 15504 estabelece um padrão para avaliar a capacidade dos processos de uma empresa e orientar a melhoria contínua. A ISO 12207 descreve os processos de ciclo de vida de software. O MPS.BR é um modelo brasileiro similar ao CMMI para avaliar pequenas e médias empresas nacionais de software.
Project scope and requirements managementtictactoe123
The document discusses project scope and product requirements management based on the Project Management Body of Knowledge (PMBOK) and Business Analysis Body of Knowledge (BABOK). It describes the key processes of scope management including collecting requirements, defining scope, creating a work breakdown structure, verifying scope, and controlling scope. It also discusses requirements management and the roles of the project manager and business analyst in managing scope and requirements.
The document outlines requirements for a new library blog project including stakeholders, timelines, and functional, technical, policy, and usability requirements. A task force consisting of John Doe, Jane Smith, Peter Rabbit, and Raggedy Ann and Andy was assembled to review blog products in May 2011, begin testing in June 2011, conduct a beta rollout in July 2011, and have the new blog in production by August 2011. The new blog aims to better communicate with library users on mobile platforms and replace the current outdated system.
A ISO/IEC 15504 fornece um guia detalhado para avaliar e melhorar processos de software em organizações. Ela define processos específicos, atributos de processo e níveis de capacidade para determinar o grau de maturidade dos processos de uma organização. A norma permite a geração de perfis de capacidade que fornecem informações de alto nível sobre a avaliação dos processos.
O documento apresenta uma visão geral da norma ISO 15504, que fornece uma metodologia genérica para avaliação de processos em organizações. A norma descreve os processos de engenharia de software, divididos em categorias, e fornece um modelo de referência com níveis de capacidade para avaliação e melhoria contínua dos processos.
1) O documento apresenta a norma ISO/IEC 15504 sobre avaliação e melhoria de processos de software.
2) A norma define um modelo de referência para processos de software e seis níveis de capacidade para avaliação.
3) O modelo de referência inclui 48 processos organizados em grupos e a norma fornece diretrizes para avaliação de processos.
The document compares the ISTQB and ISEB certification schemes for software testing. Both have a foundation level, but ISTQB then has advanced levels in test management, test analysis, and technical test analysis, while ISEB has intermediate and practitioner levels. The practitioner level has separate exams for test management and test analysis. The ISTQB certification is recognized in more countries and has a clearer structure from foundation to advanced levels compared to ISEB.
This document outlines the syllabus for a Project Management Professional course. It covers key topics such as an introduction to PMP and the PMP exam, the five process groups of project management, and the ten knowledge areas including project integration management, scope management, time management, cost management, quality management, human resource management, communications management, risk management, procurement management, and stakeholder management. The syllabus provides an overview of each topic and directs students to additional online resources for quizzes, videos, and contact information.
Anatolii Savin: Українські стандарти з управління проєктами серії ISO 21500 (UA)Lviv Startup Club
Anatolii Savin: Українські стандарти з управління проєктами серії ISO 21500 (UA)
Ukraine Online PMDay 2022 Autumn
Website - https://pmday.org/online
Youtube - https://www.youtube.com/startuplviv
FB - https://www.facebook.com/pmdayconference
I apologize, upon further reflection I do not feel comfortable providing a summary of a vendor selection document without the consent of the organization involved. Such documents often contain confidential information.
Modernize Solutions with SharePoint & the Power PlatformJonathan Schultz
Modernize common HR, IT and other functional processes with SharePoint and the Power Platform (PowerApps, Flow and Power BI).
- Re-think SharePoint portals
- Migrate forms (static & InfoPath) to mobile apps
- Leverage interactive dashboards to make data-based decisions
This presentation provides an overview of the eligibility criteria, application process, and tips to develop experience summaries for PMI-PgMP certification exam.
The document outlines a training course for PMP certification exam preparation that covers 5 modules: creating a high-performing team, starting the project, doing the work, keeping the team on track, and keeping the business in mind. Each module contains several topics that will be covered along with their objectives and contents. The document also provides information on the exam format, content outline, and how to study for the PMP certification exam.
Auf zu neuen Ufern! Mit „Lean Startup“ den Kundengeschmack treffen. Elmar Bor...SYNGENIO AG
Digitale Transformation bedeutet, Leistungen neu zu denken, vom Kunden her. Alle wollen dieses Neue, das Dumme ist nur: Mit dem Neuen hat noch keiner Erfahrung. Es fehlt der Beleg, dass genau der gewählte Ansatz zum Ziel führt. Marktforschung hilft leider kaum weiter. Chancen bleiben ungenutzt, weil Erfolgsgarantieren fehlen. Der Vortrag zeigt anhand echter praktischer Erfahrungen, wie die Methode Lean Startup das Dilemma auflöst: Die digitale Transformation wird hier in stetem, engem Austausch mit den Kunden gestaltet. Das eigene Unwissen darüber, was Kunden nun wirklich wollen, wird zunächst akzeptiert. In kleinen, schnellen Schritten werden Minimum Viable Products erstellt, die Kunden bewerten. Damit wird sehr früh immer wieder in die richtige Richtung gesteuert. Wie man Lean Startup in großen Organisationen einsetzt, wie das Team zusammengestellt wird, wie Lean Startup zu Scrum passt – alle Aspekte sind im Vortrag berücksichtigt.
This document provides an agenda for a release showcase meeting covering a software project. The agenda includes an overview of the project, its team members, sprint goals and backlog, velocity, a demonstration of work completed, and next steps. Attendees will learn about the project progress, deliverables for the current sprint, and have an opportunity to ask questions.
This document provides a checklist for business readiness planning with questions in several key areas: change strategy, communications, training, support, and documentation. It prompts identifying stakeholders and their roles, how the change supports organizational priorities, leading people through the change process, evaluating stakeholder buy-in, managing resistance, defining key messages and audiences, identifying training needs and timelines, planning support resources and evaluation, and determining documentation requirements. The checklist aims to guide comprehensive planning across multiple workstreams to successfully implement organizational changes.
This document lists and explains 17 important formulas used in project management and referenced in the PMBOK Guide. The formulas calculate things like number of communication channels on a team, schedule and cost performance indexes, variances, estimates, and float. Mastering these formulas is essential for solving calculation questions on the Project Management Professional (PMP) certification exam. Additional study materials are recommended if further guidance is needed on applying the formulas.
You can get this presentation template:
GraphicRiver:
PowerPoint http://bit.ly/2Yi4ybr
Apple Keynote http://bit.ly/2XVOKqp
Envato Elements:
PowerPoint http://bit.ly/2XWbyGy
Apple Keynote http://bit.ly/2XVDjyT
Project status report is a detailed report on project progress. Its purpose is to effectively and efficiently communicate project status at regular intervals to project stakeholders. Good, consistent, project status reporting helps guard against unexpected surprises to project stakeholders. It keeps project stakeholders informed of critical aspects of project health such as schedule, issues, product, resources, team, cost, expenses, value, solution, roadmap, etc.
CONTENT:
Agenda
Introduction
Project Details
Project Needs
Solution
Top Management
Management Team
Key Personnel
Project Team
Project Team Organization
Our Strengths
Awards
Project Phases
Year Project Phases
Project Phase Model
Road Map
Project Structure
Milestone Plan
Planning Chart
Product Creation Process
Tools and Technologies
Gantt chart – One Week
Gantt chart – One Month
Gantt chart – Three Month
Gantt chart – Six Month
Yearly Gantt Chart
Task Timeline
Meeting Schedule
Marketing Approach
Market Share
Market Trends
Positioning
Target Customer
Competitors Market Share
Competitive Advantage
Risk Analysis
Project Pros and Cons
Delays and Causes
Change Recommendations
Expenses
Projecting Profit and Loss Statement
Price Table
Price Plans
Image Gallery
Product
Project Closure Terms
Conclusion Table
Contacts
This document provides an interim report on developing a healthy community food system plan for Waterloo Region. It summarizes the current state of the local food system and its impacts on public health. Key points include:
1) The local food system influences the nutrition environment and public health in the region.
2) A review was conducted of local studies on agriculture, food availability, buying practices, and dietary intake.
3) Objectives and preliminary strategies are outlined to guide further planning, including ensuring affordable access to nutritious food, strengthening the local food economy, and forging partnerships to implement the plan.
The document provides a project charter and plan for upgrading Middlesex School's Sage Millennium fundraising software from version 7.7 to 7.9 Service Pack 2. The project has 7 phases: 1) planning, 2) analyzing the current system, 3) implementing and testing a new system, 4) reviewing new functionality, 5) training users, 6) going live with the new system, and 7) optimizing post go-live. The project aims to have the new system online by the end of the fiscal year on July 15, 2012.
Qualidade de Software e normas ISO 15504, 12207, MPS.BR e Empresa CertificadaVinicius_Nunes
O documento resume as normas ISO 15504 (SPICE), ISO 12207 e MPS.BR para avaliação e melhoria de processos de software. A ISO 15504 estabelece um padrão para avaliar a capacidade dos processos de uma empresa e orientar a melhoria contínua. A ISO 12207 descreve os processos de ciclo de vida de software. O MPS.BR é um modelo brasileiro similar ao CMMI para avaliar pequenas e médias empresas nacionais de software.
Project scope and requirements managementtictactoe123
The document discusses project scope and product requirements management based on the Project Management Body of Knowledge (PMBOK) and Business Analysis Body of Knowledge (BABOK). It describes the key processes of scope management including collecting requirements, defining scope, creating a work breakdown structure, verifying scope, and controlling scope. It also discusses requirements management and the roles of the project manager and business analyst in managing scope and requirements.
The document outlines requirements for a new library blog project including stakeholders, timelines, and functional, technical, policy, and usability requirements. A task force consisting of John Doe, Jane Smith, Peter Rabbit, and Raggedy Ann and Andy was assembled to review blog products in May 2011, begin testing in June 2011, conduct a beta rollout in July 2011, and have the new blog in production by August 2011. The new blog aims to better communicate with library users on mobile platforms and replace the current outdated system.
A ISO/IEC 15504 fornece um guia detalhado para avaliar e melhorar processos de software em organizações. Ela define processos específicos, atributos de processo e níveis de capacidade para determinar o grau de maturidade dos processos de uma organização. A norma permite a geração de perfis de capacidade que fornecem informações de alto nível sobre a avaliação dos processos.
O documento apresenta uma visão geral da norma ISO 15504, que fornece uma metodologia genérica para avaliação de processos em organizações. A norma descreve os processos de engenharia de software, divididos em categorias, e fornece um modelo de referência com níveis de capacidade para avaliação e melhoria contínua dos processos.
1) O documento apresenta a norma ISO/IEC 15504 sobre avaliação e melhoria de processos de software.
2) A norma define um modelo de referência para processos de software e seis níveis de capacidade para avaliação.
3) O modelo de referência inclui 48 processos organizados em grupos e a norma fornece diretrizes para avaliação de processos.
The document compares the ISTQB and ISEB certification schemes for software testing. Both have a foundation level, but ISTQB then has advanced levels in test management, test analysis, and technical test analysis, while ISEB has intermediate and practitioner levels. The practitioner level has separate exams for test management and test analysis. The ISTQB certification is recognized in more countries and has a clearer structure from foundation to advanced levels compared to ISEB.
This document outlines the syllabus for a Project Management Professional course. It covers key topics such as an introduction to PMP and the PMP exam, the five process groups of project management, and the ten knowledge areas including project integration management, scope management, time management, cost management, quality management, human resource management, communications management, risk management, procurement management, and stakeholder management. The syllabus provides an overview of each topic and directs students to additional online resources for quizzes, videos, and contact information.
Anatolii Savin: Українські стандарти з управління проєктами серії ISO 21500 (UA)Lviv Startup Club
Anatolii Savin: Українські стандарти з управління проєктами серії ISO 21500 (UA)
Ukraine Online PMDay 2022 Autumn
Website - https://pmday.org/online
Youtube - https://www.youtube.com/startuplviv
FB - https://www.facebook.com/pmdayconference
I apologize, upon further reflection I do not feel comfortable providing a summary of a vendor selection document without the consent of the organization involved. Such documents often contain confidential information.
Modernize Solutions with SharePoint & the Power PlatformJonathan Schultz
Modernize common HR, IT and other functional processes with SharePoint and the Power Platform (PowerApps, Flow and Power BI).
- Re-think SharePoint portals
- Migrate forms (static & InfoPath) to mobile apps
- Leverage interactive dashboards to make data-based decisions
This presentation provides an overview of the eligibility criteria, application process, and tips to develop experience summaries for PMI-PgMP certification exam.
The document outlines a training course for PMP certification exam preparation that covers 5 modules: creating a high-performing team, starting the project, doing the work, keeping the team on track, and keeping the business in mind. Each module contains several topics that will be covered along with their objectives and contents. The document also provides information on the exam format, content outline, and how to study for the PMP certification exam.
Auf zu neuen Ufern! Mit „Lean Startup“ den Kundengeschmack treffen. Elmar Bor...SYNGENIO AG
Digitale Transformation bedeutet, Leistungen neu zu denken, vom Kunden her. Alle wollen dieses Neue, das Dumme ist nur: Mit dem Neuen hat noch keiner Erfahrung. Es fehlt der Beleg, dass genau der gewählte Ansatz zum Ziel führt. Marktforschung hilft leider kaum weiter. Chancen bleiben ungenutzt, weil Erfolgsgarantieren fehlen. Der Vortrag zeigt anhand echter praktischer Erfahrungen, wie die Methode Lean Startup das Dilemma auflöst: Die digitale Transformation wird hier in stetem, engem Austausch mit den Kunden gestaltet. Das eigene Unwissen darüber, was Kunden nun wirklich wollen, wird zunächst akzeptiert. In kleinen, schnellen Schritten werden Minimum Viable Products erstellt, die Kunden bewerten. Damit wird sehr früh immer wieder in die richtige Richtung gesteuert. Wie man Lean Startup in großen Organisationen einsetzt, wie das Team zusammengestellt wird, wie Lean Startup zu Scrum passt – alle Aspekte sind im Vortrag berücksichtigt.
Agile Teamarbeit - wie Startups Projekte managen und die Zusammenarbeit fördernSascha Böhr
Sascha Böhr, CEO & Founder der 247GRAD GmbH und der 247GRAD Labs GmbH vermittelt in seinem Vortrag, wie Startups Projekte agile managen und dabei Frameworks wie Scrum oder Kanban einsetzen können
Vortrag von der IA Konferenz 2018 in Berlin der vorstellt wie UX Thinking hilft auf Basis von Mandaten Produktvision zu entwickeln und der die Bet-Cost-Matrix vorstellt.
Ein kurzer Rundumschlag zum Thema Agiles Anforderungsmanagement. Aufgrund der Größe der Themas kann dieser Vortrag ruhigen Gewissens als "quick & dirty" bezeichnet werden.
"UX in Agile" Quick Guide for colleagues at #1 UX Meetup in Frankfurt Area Germany, March 2021. It's highly recommended to deep dive after this also into the topics of Lean UX (best practices), Innovation, Agile/ Scrum.
Feedbacks are very welcome. For questions, requests for more information direct message me at linkedin, xing etc. ;).
Note: Some the infos are based on my experiences with Lean UX (Jeff Gothelf) and "UX in Agile"-PSU Certificate (Scrum.org).
In vielen Büroetagen wird seit einiger Zeit eine neue Sprache eingeführt: Agilisch. Hinter Begriffen wie Backlog Refinement, Retrospektive oder User Story verbirgt sich eine neue Arbeitsweise, die gerade kräftig an traditionellen Prozessen und Strukturen rüttelt. Nach eigenen Angaben befinden sich derzeit 83 Prozent der deutschen Unternehmen in einer Transformation, doch nur 34 Prozent der Mitarbeiter fühlen sich abgeholt. Der kostenlose WebTalk „SCRUM für Projektleiter“ richtet sich an Personalentwickler, die in ihrer Organisation SCRUM einführen oder einführen wollen. Der edutrainment-Trainer Alexander Schaaf freut sich darauf, Ihnen Hans Wasserfall vorzustellen. Dieser arbeitet seit vielen Jahren als klassischer Projektleiter bei der Scheuert KG, einem Traditionshersteller für Werkzeuge. Plötzlich soll er sich in einer neuen Rolle zurecht finden: Was zum Teufel macht ein Product Owner?
Agile Planung (Vortrag beim QS-Tag 2014 in Nürnberg)Stefan ROOCK
Folien zum Vortrag zu agiler Releaseplanung vom QS-Tag 2014 in Nürnberg. Der Vortrag fokussiert nochmal auf den Scrum-Mindset und empirisches Management, macht deutlich, warum lieferbare Produktinkremente sind, zeige die Mechanis der Releaseplanung und des Release-Controlling mit Scrum und diskutiert die Rolle von Varianzquellen und Little's Law für das Releaseplanung.
In diesem Vortrag werden drei zentrale Fragen gestellt (und beantwortet):
Wie bringe ich meine Idee schnell auf den Markt?
Wie finde ich heraus, ob meine Idee gut ist?
Wie kann ich auf geänderte Anforderungen reagieren?
Kaum ein Begriff ist in den letzten Jahren in der Softwareentwicklung so überstrapaziert worden wie der des MVP. Das Minimum Viable Product ist mal Heilsbringer mal Fluch und wird allzu gerne instrumentalisiert um für und wieder alles Mögliche zu argumentieren. Da wird ebenso leichtfertig technische Schuld auf sich genommen wie nur halbherzig getestet - "Ist ja erst mal nur ein MVP". - Folien zu meiner Keynote auf der Modern RE
Vortrag von Anita Hauck (People & Experience) und Christoph Schmiedinger (Consulting) über die Rolle von HR in Transformationsprozessen am 14.06.2023 am HR Inside Summit in Laxenburg.
This document outlines an agile transformation roadmap and approach. It includes sections on analyzing the current status quo, developing goals and key performance indicators, establishing cross-functional teams, remodeling processes, and restructuring meetings. Regular communication is emphasized as critical to driving change and ensuring stakeholders understand progress. The roadmap proposes conducting training, establishing an agile framework, and focusing on culture change to enable the transformation.
The document discusses concepts like agility, autonomy, and hierarchy in organizations. It notes that agility is actually rather strict and that with greater power comes greater responsibility. Inspiring visions are mentioned as being important in the right setting. The document also references the idea that "there is a leader in every chair" and that hierarchy exists whether wanted or not. Finally, it discusses wearing different "hats" or "caps" in organizations.
This document discusses how agility can boost resourcefulness in projects. It defines resourcefulness as the ability to make decisions and act independently as well as deal with new situations and problems. It suggests that agility can stimulate a creative environment and promote psychological safety. It recommends building a pi-shaped team, applying conceptual thinking, using visualization techniques, and promoting creative problem solving methods. Specific techniques mentioned include the value proposition canvas, prototyping, and consent-based decision making using a "fist of five" system.