The document is a review guide for a test on October 15th. It instructs students to study for the test tomorrow and to review their homework with a partner. It provides an agenda for reviewing material for Test 1 in Mod 2.
This Hands-on Agile webinar addresses twelve familiar sprint anti-patterns: from gold-plating, delivery Y instead of X, to absenteeism, side-gigs, and organizing people instead of the flow of work.
There is a SlideShare bug that prevented the first slide from being displayed completely — the word “Retrospective” is not shown. My apology!
This Hands-on Agile webinar covers twelve anti-patterns of the sprint retrospective—from #NoRetro to the dispensable buffer to UNSMART action items to a missing product owner.
The sixth Hands-on Agile webinar addresses product owner anti-patterns. Learn 12 ways to improve a product owner’s skill set and when you — as the scrum master or scrum team — should reach out to your product owner and offer support.
This Hands-on Agile mini-series addresses 12 familiar Scrum Sprint Review anti-patterns: death by PowerPoint to side-gigs to none of the stakeholders cares to attend.
NEWSLETTER — join more than 20,000 peers: https://age-of-product.com/subscribe/?ref=youtube
BLOG: “Sprint Review Anti-Patterns”: https://age-of-product.com/webinar-sprint-review/
This Hands-on Agile mini-series addresses 12 familiar Scrum Master anti-patterns: from the agile manager to the team secretary to dogmatism.
Let us start with a short refresher from the Scrum Guide. According to it, the “Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand the theory, practices, rules, and values of Scrum. The Scrum Master is a servant-leader for the Scrum Team.” Finally, the “Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.”
(1) The first Scrum Master anti-pattern covers the agile manager. Self-organization does not mean the absence of management: why handle pay-role as a Scrum Team? Outsourcing of tasks to the management is hence common. However, Scrum is by all means not about exercising command & control; the Scrum master is not a supervisor.
(2) The second Scrum Master anti-pattern covers the Scrum team secretary and Scrum parents. The Scrum parent is generally shielding the team from the cold and cruel world, creating a safe & happy agile bubble.
(3) The third Scrum Master anti-pattern covers the imposter. Dolla, dolla, bill ya'll—the Scrum Master imposter believes that this agile/scrum thingy is a fad—how hard can it be, the Scrum Guide is just 17 pages.
(4) The fourth Scrum Master anti-pattern covers Scrum dogmatism. The Scrum Master enjoys teaching (and never leaves the Shu-phase).
(5) The fifth Scrum Master anti-pattern covers failing at the capacity game. The Scrum master does not address the necessity of slack time by fighting the push for 100% utilization.
(6) The sixth Scrum Master anti-pattern covers the flow undermining Scrum Master. The Scrum Master allows stakeholders to disrupt the flow of the development team during the sprint.
(7) The seventh Scrum Master anti-pattern covers the Scrum Master with a metrics fetish, pursuing flawed metrics. The Scrum Master keeps track of individual performance metrics such as story points per developer per sprint.
(8) The eighth Scrum Master anti-pattern covers the Scrum Master ignoring Scrum values.
(9) The ninth Scrum Master anti-pattern covers the skipped Retrospective. All Scrum events are essential for a team’s success—you cannot skip any event.
(10) The tenth Scrum Master anti-pattern covers the Groundhog-Day retrospective. The retrospective never changes in composition, venue, or length. In this case that the team will likely revisit the same issues over and over again—it’s groundhog day without the happy ending, though.
(SUMMARY) The last chapter summarizes my dirty dozen of Scrum Master anti-patterns: from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.
This Hands-on Agile webinar addresses twelve familiar sprint anti-patterns: from gold-plating, delivery Y instead of X, to absenteeism, side-gigs, and organizing people instead of the flow of work.
There is a SlideShare bug that prevented the first slide from being displayed completely — the word “Retrospective” is not shown. My apology!
This Hands-on Agile webinar covers twelve anti-patterns of the sprint retrospective—from #NoRetro to the dispensable buffer to UNSMART action items to a missing product owner.
The sixth Hands-on Agile webinar addresses product owner anti-patterns. Learn 12 ways to improve a product owner’s skill set and when you — as the scrum master or scrum team — should reach out to your product owner and offer support.
This Hands-on Agile mini-series addresses 12 familiar Scrum Sprint Review anti-patterns: death by PowerPoint to side-gigs to none of the stakeholders cares to attend.
NEWSLETTER — join more than 20,000 peers: https://age-of-product.com/subscribe/?ref=youtube
BLOG: “Sprint Review Anti-Patterns”: https://age-of-product.com/webinar-sprint-review/
This Hands-on Agile mini-series addresses 12 familiar Scrum Master anti-patterns: from the agile manager to the team secretary to dogmatism.
Let us start with a short refresher from the Scrum Guide. According to it, the “Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand the theory, practices, rules, and values of Scrum. The Scrum Master is a servant-leader for the Scrum Team.” Finally, the “Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.”
(1) The first Scrum Master anti-pattern covers the agile manager. Self-organization does not mean the absence of management: why handle pay-role as a Scrum Team? Outsourcing of tasks to the management is hence common. However, Scrum is by all means not about exercising command & control; the Scrum master is not a supervisor.
(2) The second Scrum Master anti-pattern covers the Scrum team secretary and Scrum parents. The Scrum parent is generally shielding the team from the cold and cruel world, creating a safe & happy agile bubble.
(3) The third Scrum Master anti-pattern covers the imposter. Dolla, dolla, bill ya'll—the Scrum Master imposter believes that this agile/scrum thingy is a fad—how hard can it be, the Scrum Guide is just 17 pages.
(4) The fourth Scrum Master anti-pattern covers Scrum dogmatism. The Scrum Master enjoys teaching (and never leaves the Shu-phase).
(5) The fifth Scrum Master anti-pattern covers failing at the capacity game. The Scrum master does not address the necessity of slack time by fighting the push for 100% utilization.
(6) The sixth Scrum Master anti-pattern covers the flow undermining Scrum Master. The Scrum Master allows stakeholders to disrupt the flow of the development team during the sprint.
(7) The seventh Scrum Master anti-pattern covers the Scrum Master with a metrics fetish, pursuing flawed metrics. The Scrum Master keeps track of individual performance metrics such as story points per developer per sprint.
(8) The eighth Scrum Master anti-pattern covers the Scrum Master ignoring Scrum values.
(9) The ninth Scrum Master anti-pattern covers the skipped Retrospective. All Scrum events are essential for a team’s success—you cannot skip any event.
(10) The tenth Scrum Master anti-pattern covers the Groundhog-Day retrospective. The retrospective never changes in composition, venue, or length. In this case that the team will likely revisit the same issues over and over again—it’s groundhog day without the happy ending, though.
(SUMMARY) The last chapter summarizes my dirty dozen of Scrum Master anti-patterns: from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.
10 times better pm with kanban BestBrainsBestBrains
"Project Manager"? Isn't that something Agile consultants have spent the last 10+ years trying to get rid off? Well they are still here and some of them are actually sensible people that do a damn good job under challenging circumstances. No matter if you are an old time micro managing PM or have caught the Agile wave and transitioned into a Product owner or Scrum Master role Kanban can help you shine!
In this presentation we will focus on how Kanban can help you become a better PM and increase effectiveness, alignment and motivation with more predictable outcomes and increased customer value and satisfaction - even in situations where innovation is of the essence and Agile principles guide you to embrace change underway. Don't believe me? Well fortunately I have real data to prove the points.
Since Kanban is principle based you can even keep centralizing control, work delegation and the belief that heavy upfront specification is the best way to work. Chances are that in time you will get tired of it and find that there are more effective ways of administering teams and projects but initially Kanban does not make any judgements as to the optimal way of work in your situation. Come along and be inspired, provoked and maybe even enlightened.
The third Hands-on Agile webinar product addresses backlog anti-patterns — from out-dated and oversized tickets to the part-time proxy product owner and his or her idea repository.
Learn more about the numerous product backlog anti-patterns that can manifest themselves when you try to create value for your customers and your organization.
BLOG: https://age-of-product.com/webinar-product-backlog/
YOUTUBE: https://www.youtube.com/watch?v=fCE1PmtbGXQ
ng-japan 2018 https://ngjapan.org/
にてお話しした「Protractor under the hood」の資料です。
angular-cli の e2eテストコマンド ng e2e の裏側で、Protractorがどんな仕組みを作ってテストを実行しているかについてお話ししました。
動画はこちらです。
https://youtu.be/_eMrDsLjIOM?t=13345
10 times better pm with kanban BestBrainsBestBrains
"Project Manager"? Isn't that something Agile consultants have spent the last 10+ years trying to get rid off? Well they are still here and some of them are actually sensible people that do a damn good job under challenging circumstances. No matter if you are an old time micro managing PM or have caught the Agile wave and transitioned into a Product owner or Scrum Master role Kanban can help you shine!
In this presentation we will focus on how Kanban can help you become a better PM and increase effectiveness, alignment and motivation with more predictable outcomes and increased customer value and satisfaction - even in situations where innovation is of the essence and Agile principles guide you to embrace change underway. Don't believe me? Well fortunately I have real data to prove the points.
Since Kanban is principle based you can even keep centralizing control, work delegation and the belief that heavy upfront specification is the best way to work. Chances are that in time you will get tired of it and find that there are more effective ways of administering teams and projects but initially Kanban does not make any judgements as to the optimal way of work in your situation. Come along and be inspired, provoked and maybe even enlightened.
The third Hands-on Agile webinar product addresses backlog anti-patterns — from out-dated and oversized tickets to the part-time proxy product owner and his or her idea repository.
Learn more about the numerous product backlog anti-patterns that can manifest themselves when you try to create value for your customers and your organization.
BLOG: https://age-of-product.com/webinar-product-backlog/
YOUTUBE: https://www.youtube.com/watch?v=fCE1PmtbGXQ
ng-japan 2018 https://ngjapan.org/
にてお話しした「Protractor under the hood」の資料です。
angular-cli の e2eテストコマンド ng e2e の裏側で、Protractorがどんな仕組みを作ってテストを実行しているかについてお話ししました。
動画はこちらです。
https://youtu.be/_eMrDsLjIOM?t=13345
With IntraDoc, you can create a document managment Intranet site in less thn five minutes.
This presentation shows the basics of the intranet site creation (intranet title, intranet url, site structure, adding documents). It shows a step-by-step to create your first intranet site.
I explained how FiNC Developer implement APIs.
What gems and what development process we use.
We switched api gems from grape and rabl to ApplicationController and ActiveModelSerializer.
I explained why and its pros/cons.
Introduction to AI for Nonprofits with Tapp NetworkTechSoup
Dive into the world of AI! Experts Jon Hill and Tareq Monaur will guide you through AI's role in enhancing nonprofit websites and basic marketing strategies, making it easy to understand and apply.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
Embracing GenAI - A Strategic ImperativePeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.