Devops for Growth
107.5K views | +8 today
Follow
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'PSPO 1'. Clear
Scooped by Mickael Ruau
Scoop.it!

How to Sabotage A Scrum Master — 44 Anti-Patterns from the Trenches

How to Sabotage A Scrum Master — 44 Anti-Patterns from the Trenches | Devops for Growth | Scoop.it
How to Sabotage A Scrum Master: 44 Anti-Patterns from the Trenches to Avoid — Scrum Master Survival Guide #11 by PST Stefan Wolpers...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Hiring a Professional Product Owner

Hiring a Professional Product Owner | Devops for Growth | Scoop.it

 

Role Summary (Accountabilities)

This Product Owner is a key position that sets the tone for product leadership and the definition of success in the organization. As such, modern product management practices and mindset are expected to be put into practice daily. This Product Owner is accountable for and has the authority to maximize the value of the product and the effectiveness of the Product Backlog by using, but not limited to, these 6 key stances:

  • The Visionary
    • Articulating the strategic vision of the product;
    • Developing and explicitly communicating intermediate strategic goals;
    • Propose how the product can tactically increase its value each Sprint;
    • Understand and shape the impact of the product on our company;
    • Each Sprint ensuring that the Scrum Team is prepared to discuss the most important Product Backlog items;
  • The Influencer
    • Actively manage stakeholders, their desires, expectations, and outcomes;
    • Create an effective communication strategy;
    • Influence the Developers during Backlog Items Sizing by helping them select and understand trade-offs;
    • Work with Developers daily to clarify and renegotiate the Scope of the Sprint;
  • The Collaborator
    • Collaborating closely with the Developers & Stakeholders daily;
    • Developing and communicating budget, investments, roadmaps, vision, & strategy;
    • Developing controls for a change, risk, quality, & incident management to enable professional Scrum;
    • Developing and influencing commercial contracts that align with the agile values and principles;
  • The Customer Representative
    • Understand the desired outcomes of customers within the bounds of the business constraints
    • Defining our product(s) and services and how customers will interact with them
  • The Decision Maker
    • Ensuring that the Product Backlog is transparent, visible and understood;
    • Ordering Product Backlog items;
    • Choosing what and when to release;
  • The Experimenter
    • Using evidence-based management techniques to optimise outcomes and value delivered;
    • Create hypothesis and craft experiments to test that hypothesis quickly;
    • Tracking product use and impact on end-users and drive consistent approaches across all Product Verticals;

The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.

Mickael Ruau's insight:

Role Requirements

The successful candidate must have the following attributes:

  • First level Scrum Product Owner certification (CSPO, PSPO I);
  • Product Owner Experience; Demonstrable experience of product ownership;
  • Business domain knowledge; a keen understanding of the [business domain], market, and other influencers;
  • Entrepreneurial focus; A keen understanding of evidence-based techniques to inform strategic and tactical milestones;
  • Excellent ideation skills; with a proven track record of successful hypothesis-driven ideation and sustainable feedback loops;
  • Excellent communication skills; Communicating Vision, Goals, and Backlog Items with both the Developers and other Stakeholders;

In addition, the successful candidate will have some or all of the following attributes:

  • Second level Scrum Product Owner certification (A-CSPO, PSPO II);
  • Experience fulfilling the Product Owner role for at least two years;
  • Knowledge and/or experience with complimentary Agile product management techniques: Evidence-based Management, Goal-orientated Product Roadmap, Business Model Canvas, Growth Experiment Canvas, Delegation Poker, Liberating Structures, Three Horizons Innovation, Stakeholder Mapping, Impact Mapping, Value Pyramids;

I would love to get your feedback and discussion on this job specification so that we can make it better!

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

5 Tasks Product Owners Should Say ‘No’ To - Agile

5 Tasks Product Owners Should Say ‘No’ To - Agile | Devops for Growth | Scoop.it
Many a time, product owners are given tasks that fall beyond their job description. Read the tasks product owners should not do.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Tips for the PSM I, PSPO I, and PSK Exams :: Management Plaza

Tips for the PSM I, PSPO I, and PSK Exams :: Management Plaza | Devops for Growth | Scoop.it
Now that you're done learning Scrum and/or Kanban, it's time to review a few tips that will be useful in your PSM I, PSPO I, or PSK exam.
Mickael Ruau's insight:

Be Careful with Compatibility

There are many resources for Scrum and Kanban, but not all of them are compatible with these exams — even some of them that come from reputable authors. So, be careful with that.

How Many Choices?

The PSM, PSPO, and PSK exams are not normal multiple‑choice exams. You may have questions that ask you to select more than one choice (e.g., Which two of the following are…). You wouldn’t believe how many people miss that and just pick one choice!

So, read the question carefully to understand when more than one choice is required. Sometimes, the question specifies the number of choices, and sometimes it just tells you to pick multiple choices. The choices in these questions have check-boxes (small squares) instead of radio buttons (small circles); so, make sure you get used to noticing that as well.

NOT!

“Which of the following is NOT a responsibility of…”

“All of the following are responsibilities of… EXCEPT for…”

Sadly, many people miss these capitalized negative words and pick the wrong answer. This is more common when the question is more complicated and you become so engaged in assessing the correctness of the statements that you forget the question was asking for the wrong statement instead of the right one.

Be very careful with this type of question, and pay serious heed to it if you make this mistake in your simulated exams.

Damned Details!

You know that the Daily Scrum meetings are for the Development Team members, and only they are required to attend the meeting. Others can still go there and observe them — even people from other projects (to learn something new from them) — but they only observe, and they shouldn’t talk.

Take these statements:

  1. The Product Owner can attend the Daily Scrum meetings.
  2. The Product Owner can participate in the Daily Scrum meetings.

Are these statements true or false?

The first one is simple: It’s true. The second one, however, is false because “participate” implies engagement, whereas everyone except the Development Team members is only supposed to be observing.

There are many questions like this, where a single word changes everything. You need to be careful with it.

Modal Verbs

Let’s continue the example from the previous tip. What do you think about the following statements?

  1. The Product Owner can attend the Daily Scrum meetings.
  2. The Product Owner should attend the Daily Scrum meetings.

While the first statement is true, the second one is false, and it’s all because of the modal verbs. It’s correct that the Product Owner is allowed to attend the meeting, but it doesn’t mean that it’s necessary for them to be there.

In case you’re wondering, in the exam, “can” means “may”, and “should” means “ought to”/“required to”, similarly to the way English is used by most people nowadays.

Look It Up!

The PSM, PSPO, and PSK exams are in open-book format, so, you should make sure you take advantage of that. Have a copy of the Scrum Guide (and also the Kanban for Scrum Teams Guide for the PSK exam) open and ready for reference. As well as this, while you’re practicing with the sample questions, write down all the points that are troubling you, organize them, and have them ready to use during your exam. It’s better to write your notes in a file rather than on paper, so that you can search them easily.

Note that the amount of time you have for each question is less than what you have in most other exams, and you can only look up the concepts when you’ve had enough practice, you manage your time perfectly, and you’re completely familiar with the resources you’re using. So, again, remember to practice this in your simulated exams.

The Scrum Guide

Things would have been much easier if the Scrum Guide could be used to answer every question, but that’s not the case. Most questions in the exam cannot be answered based solely on the Scrum Guide, so, don’t expect otherwise.

Besides the above, some questions in the exam are based on certain interpretations of the Scrum Guide (the way Scrum.org sees it). For example, how many Product Owners do we have in scaled Scrum? One of the co-authors of the Scrum Guide believes that there must be one and only one Product Owner, no matter how many teams you have, while the other co-author believes that it’s a good idea to have multiple Product Owners, and a Chief Product Owner. Which one do you think is supported in the Scrum Guide? Both!

Finally, some points in the Scrum Guide are not clear enough; for example, the number of Definitions of Done for multiple teams, and what most people understand based on the guide, which is different from what they are expected to answer in the exam.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Je dois réaliser un Product Backlog, à l’aide !

Je dois réaliser un Product Backlog, à l’aide ! | Devops for Growth | Scoop.it
Les 6 points clés à connaitre pour réaliser votre premier backlog produit, avec en bonus un exemple de backlog et le glossaire Scrum à maitriser !
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Les Rôles du Scrum Product Owner

Rôle du Scrum Product Owner Jeff Patton Agile Product Design jpatton@acm.org Traduit par Fabrice Aimetti le 6-Fév-2010
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Defining a Product | Agile Product Management | InformIT

Defining a Product | Agile Product Management | InformIT | Devops for Growth | Scoop.it
Organizations which design systems . . . are constrained to produce designs which are copies of the communication structures of these organizations.6

The result of Conway’s Law is a series of interconnected “systems” built by different departments (or hierarchies) within an organization with little focus on the actual product or on who the customer even is.

This is the reason Scrum names the role Product Owner and not System, Feature, or Component Owner.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Product Management and Scrum | Agile Product Management | InformIT

Product Management and Scrum | Agile Product Management | InformIT | Devops for Growth | Scoop.it
Two scrum professionals lay down the foundations of Agile Product Management and introduce the three Vs (vision, value, validation) as a way to achieve maximize the ROI of a product.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Product Mindset versus Project Mindset | Agile Product Management | InformIT

Product Mindset versus Project Mindset | Agile Product Management | InformIT | Devops for Growth | Scoop.it
Two scrum professionals lay down the foundations of Agile Product Management and introduce the three Vs (vision, value, validation) as a way to achieve maximize the ROI of a product.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Tout sur les certifications Agile Scrum.org | by Aline Denys | maytheforce.bewizyu

Tout sur les certifications Agile Scrum.org | by Aline Denys | maytheforce.bewizyu | Devops for Growth | Scoop.it
reprendre la base du Scrum, celle ci étant consignée dans le Scrum Guide, disponible ici en français, et aussi ici dans beaucoup d’autres langues.

En tant que francophone, vous allez certainement, selon votre niveau d’anglais, avoir un peu de mal à intégrer tout le vocabulaire. Pour ce faire, lisez et relisez le Scrum Guide en français, puis en anglais. Le dual screen est aussi un bon exercice pour bien intégrer les notions dans les deux langues.

Voici quelques éléments de vocabulaire souvent repris dans les questions et les réponses proposées dans le QCM PSM1, histoire de vous donner un aperçu du niveau attendu :
impediment / prevent / stakeholder / improvement / accountability / increase / requirements / enhancements / trade-offs / remain / forecast / solely / throughout / useable / involved / sustain / assert / commit / scope / provide / accountable / track / struggling / occur / least / scale
Mickael Ruau's insight:
Est ce que beaucoup de personnes sont certifiées Scrum.org ?

Quelques chiffres mis à jour le 01/06/2019, que vous retrouverez ici sous forme de tableau :

 
Nombre de personnes certifiées Scrum.org au 01/06/2019 par rapport à la date de création de la certification

Nous pouvons observer que les premiers niveaux de certifications, étant prisés, sont victimes de leur succès. Cependant, il est estimé que le taux de réussite ne dépasse pas les 30% toutes certifications confondues.

N’hésitez pas à construire votre propre plan de certifications correspondant au but que vous vous êtes fixé.

A lire : Un article intéressant (en anglais) sur l’optimisation de l’ordre de passage des certifications Scrum.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Les 10 pièges à éviter pour réussir sa certification Scrum Master et Product owner

Les 10 pièges à éviter pour réussir sa certification Scrum Master et Product owner | Devops for Growth | Scoop.it
Vous souhaitez décrocher la certification Professional Scrum Master et Professional Product Owner ? Découvrez les 10 pièges à éviter pour réussir !
Mickael Ruau's insight:

Bien que conseillé par le Scrum Guide, les « progress monitors » tels que le burndown chart, le burnup chart, …  ne sont pas obligatoires en Scrum et sont des exemples d’outils possibles parmi d’autres pour mesurer l’avancement de l’équipe dans son développement et l’atteinte de son objectif. Il est bien précisé et vous serez à plusieurs reprises questionner sur l’empirisme qui prime sur les outils.

 

Modifier une équipe, comme l’agrandir par exemple en accueillant un nouveau collaborateur impacte son organisation et peut donc diminuer sa vélocité dans un premier temps. Ne soyez pas trop rapide sur cette question en répondant spontanément que cela accélère la productivité de l’équipe. Dans un premier temps, il est peu probable que la productivité de votre équipe s’améliore à l’arrivée d’un nouveau collaborateur dans l’équipe de développement. Et n’oubliez pas, multiplier par 2 votre équipe ne vous permettra pas pour autant de multiplier en 2 votre production.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Suggested Reading for Professional Scrum Product Owner™ I

Suggested Reading for Professional Scrum Product Owner™ I | Devops for Growth | Scoop.it
The PSPO I assessment includes questions from the following Focus Areas as defined in the Professional Scrum Competencies.

Understanding and Applying the Scrum Framework:
Empiricism, Roles, Events, Artifacts, Done.
Developing People and Teams:
Self-Organizing Teams, Leadership.
Managing Products with Agility:
Forecasting & Release Planning, Product Vision, Product Value, Product Backlog Management, Business Strategy, Stakeholders & Customers.

Your primary study resource should be the Product Owner Learning Path, and since the Product Owner works very closely with the Scrum Master and Development Team, it will be beneficial to become familiar with material in the Scrum Master Learning Path.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

How to pass PSPO-1: Self Study: Thoughts & Tactics | by Sanjeev Ramani

How to pass PSPO-1: Self Study: Thoughts & Tactics | by Sanjeev Ramani | Devops for Growth | Scoop.it

 

1) I would highly recommend attempting PSM-1 certification prior to PSPO-1. There are many overlapping subject areas, and thoroughness in PSM-1 preparation covers more than half the material required for PSPO-1.

You can find my post on PSM-1 preparation here: How-to-pass-psm-1-self-study-thoughts-tactics

2) The following are the major subject areas for PSPO-1 certification

a) Agile Product Management: PSM-1 preparation is sufficient. Additionally, focus on how a product owner would envision a product’s life in an agile environment. If you have time, learn about Business Model Canvas and Value Proposition. It would help in understanding how a product owner would define the customer segments, value proposition, key activities etc.

b) Value Driven Development: Put yourself in a Product Owner’s shoes, and visualize how you would enhance the product’s value. This would involve defining and measuring key metrics that are likely to increase your product’s value and ROI.

Read the Evidence Based Management Guide. The guide covers the key metrics used for measuring a product’s value and you can expect a few questions in your assessment on this topic.

Link to the EBMgt guide: Evidence-based-management-guide

c) Scrum Theory & Empiricism: PSM-1 preparation is sufficient.

d) Scrum Framework: PSM-1 preparation is sufficient.

e) Product Backlog Management: PSM-1 preparation would cover a significant portion of this subject area. A very good source that explains the nuances of Product Backlog Management is the “Scrum Crazy New Product Owner” blog. Additionally, learn about user stories, acceptance criteria, estimation techniques like planning poker etc.

Link: Scrum Crazy New New Product Owner

f) Release Management: This subject area involves the release strategies that a Product Owner would employ. Once again, the “Scrum Crazy New Product Owner” blog covers good ground on this topic. Additionally, learn about velocity, cone of uncertainty, customer absorption etc.

3) Scrum.org provides free open assessments for both “scrum master” and “product owner” subject areas that test your basic understanding. Attempt these as many times as you can.

4) Apart from the scrum open assessments for the above roles, I would encourage you to attempt the other open assessments available for Nexus and Developer. This will enrich your overall understanding of scrum.

Link to all scrum open assessments: https://www.scrum.org/open-assessments

5) Mikhail Lapshin has prepared a wonderful quiz for PSPO-1 aspirants, similar to his PSM-1 quizzes. A combination of the PSPO and the PSM quizzes would ensure good coverage of the scrum guide.

Link: http://mlapshin.com/index.php/scrum-quizzes/

6) The only assessments I took up during preparation were the scrum.org open assessments and Mikhael Lapshin’s quiz. There are many commercially available assessment packages, but I would refrain from commenting on them, since I have not used them. However, if you have covered the topics mentioned above, you might not have any real use for them.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The 2 Best Product Owners I Ever Worked With – The Empowered Product Owner

The 2 Best Product Owners I Ever Worked With – The Empowered Product Owner | Devops for Growth | Scoop.it
A few years back I wrote 2 popular posts that talked about the best Scrum Masters I ever worked with. This time around I am going to share some stories about the best Product Owners I have encountered.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Plusieurs product owner dans une équipe ?

Plusieurs product owner dans une équipe ? | Devops for Growth | Scoop.it
Contexte fréquent avec plusieurs product owner

En effet dans certaines structures, l’agilité n’est pas encore un pilier de sa culture. Et il n’est pas rare de voir des « dits » product owner qui ne sont pas liés à un produit mais à une expertise particulière sur de gros produits.

Et ce type d’organisation complexifie considérablement le travail des équipes qui tentent tant bien que mal à mettre du Scrum en place. Doit-on dire à ces équipes d’abandonner Scrum ou les aider à faire face à ce contexte ? Après tout, tout un travail de réorganisation peut se faire en parallèle pour améliorer ce contexte complexe.

Partant dans l’idée d’aider les équipes, nous allons voir quelques astuces non négligeable pour améliorer ce type de contexte.
Plusieurs product own
Mickael Ruau's insight:

Le Scrum Guide dit NON !

Alors si nous nous arrêtons sur le Scrum Guide, il est assez formel sur le sujet :

Une équipe Scrum comprend un Product Owner, une équipe de développement (Development Team) et un Scrum Master.

scrum guide fr

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

How to Pass the Professional Scrum Product Owner Level I (PSPO I)

How to Pass the Professional Scrum Product Owner Level I (PSPO I) | Devops for Growth | Scoop.it
The PSPO I is the foundation level product owner certification available through Scrum.org. Here's how to pass it on your firs
Mickael Ruau's insight:

Here are a couple key concepts to remember that might be different from what you may have learned or heard elsewhere:

  • The Scrum guide does not define a pre-planning stage (iteration 0), and the goal of the first sprint is a potentially releasable product. Many agile teams across industries include these, but they are not part of the official Scrum framework. 
  • Understand the underlying empirical control process that is the basis for all Agile processes. Empiricism exercises control through focusing on Transparency, Inspection, and Adaption in a similar model to the Scientific method.
  • Scrum Guide defines a Sprint Goal and only allows canceling the sprint if the goal becomes obsolete, which is determined by the product owner.
  • The Scrum Guide includes heavy emphasis on structured autonomy of the Scrum team. The people doing the development understand best what is involved in needing to build a quality, potentially releasable product every sprint. 
  • The product owner is responsible for maximizing value of the work the Scrum team completes. While the product owner is responsible for the product backlog and its “ordering”, they do not have to do all the work to accomplish this. They can work with and rely on the Scrum team to do so.
  • A good product owner does not control all the flow of information to/from the team, but helps connect the team with whoever is needed (stakeholders, users, technical leads, other business representatives, etc.) so they can get the most direct answer possible with minimal lag time or handoff loss. 
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Changes in the 2020 Scrum Guide: Q&A with Ken Schwaber and Jeff Sutherland

Changes in the 2020 Scrum Guide: Q&A with Ken Schwaber and Jeff Sutherland | Devops for Growth | Scoop.it
The Scrum Guide has been updated to make it less prescriptive, using simpler language to address a wider audience. These changes have been done to make Scrum a “lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems”. An interview with Ken Schwaber and Jeff Sutherland about the changes to the guide.
Mickael Ruau's insight:

Key Takeaways

  • Over the years, the Scrum Guide started getting a bit too prescriptive. The 2020 version brings Scrum back to being a minimally sufficient framework by removing or softening prescriptive language.
  • The 2020 Scrum Guide has placed an emphasis on eliminating redundant and complex statements as well as removing any remaining inference to IT work, and is now only 13 pages long.
  • The 2020 version brings together everyone as one team, the Scrum Team, while previous versions had the Development Team within the Scrum Team.
  • The three artifacts, Product Backlog, Sprint Backlog and Increment now contain ‘commitments’ to them. For the Product Backlog it is the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done.
  • It is important for teams to remember that Scrum is still Scrum. Scrum is a framework. It describes the bare minimum to enable a team to work on complex work.
 

The Scrum Guide has been updated to make it less prescriptive, using simpler language to address a wider audience. These changes have been done to make Scrum a "lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems".

The changes between 2017 and 2020 Scrum Guides are:

  1. Even less prescriptive
  2. One team, focused on one product
  3. Introduction of product goal
  4. A home for Sprint Goal, Definition of Done, and Product Goal
  5. Self-managing over self-organizing
  6. Three sprint planning topics
  7. Overall simplification of language for a wider audience
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

[2 Mins FAQ] Can One Person Be Both The Scrum Master And The Product Owner?

Starting from today, I am going to start a new series on my channel which I will call the 2 minutes FAQ series.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Comprendre le rôle de Product owner en 1 minute

Comprendre le rôle de Product owner en 1 minute | Devops for Growth | Scoop.it
L’essentiel à connaître pour devenir Product owner, avec en bonus le Mémo et la Checklist à télécharger pour être un bon Product owner au quotidien !
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Product Owner | Agile Product Management | InformIT

The Product Owner | Agile Product Management | InformIT | Devops for Growth | Scoop.it
Two scrum professionals lay down the foundations of Agile Product Management and introduce the three Vs (vision, value, validation) as a way to achieve maximize the ROI of a product.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Product Management Vacuum and the Three Vs | Agile Product Management | InformIT

The Product Management Vacuum and the Three Vs | Agile Product Management | InformIT | Devops for Growth | Scoop.it
Two scrum professionals lay down the foundations of Agile Product Management and introduce the three Vs (vision, value, validation) as a way to achieve maximize the ROI of a product.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Q&A on the Book The Professional Product Owner

Q&A on the Book The Professional Product Owner | Devops for Growth | Scoop.it



Key Takeaways

Product Owners need to be more than scribes or proxies; they are true agile product managers
Scrum is a tool for agile product delivery, not for project management
The Professional Product Owner has an entrepreneurial mind set
The Professional Product Owner is responsible for the Vision, Value and Validation of the product
Scale your Product, not your Scrum

The book The Professional Product Owner explains what Product Owners can do to become real entrepreneurs who initiate and drive products, and what teams can do to release frequently. It provides ideas and personal anecdotes for effectively applying the Scrum Product Owner role and activities.

InfoQ readers can download an excerpt from The Professional Product Owner.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

L'ebook du Scrum master certifié | Certification Scrum

L'ebook du Scrum master certifié | Certification Scrum | Devops for Growth | Scoop.it
Augmente tes chances de réussite à la certification de Scrum master ou Product owner (PSPO I ou PSM I) en téléchargeant l’ebook gratuit.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Peopleware: Productive Projects and Teams - Wikipedia

Peopleware: Productive Projects and Teams

Peopleware: Productive Projects and Teams is a 1987 book on the social side of software development, specifically managing project teams. It was written by software consultants Tom DeMarco and Tim Lister, from their experience in the world of software development. This book was revised in 2013.

Mickael Ruau's insight:

Peopleware is a popular book about software organization management. The first chapter of the book claims, "The major problems of our work are not so much technological as sociological in nature". The book approaches sociological or 'political' problems such as group chemistry and team jelling, "flow time" and quiet in the work environment, and the high cost of turnover. Other topics include the conflicts between individual work perspective and corporate ideology, corporate entropy, "teamicide" and workspace theory.

 

The authors presented most subjects as principles backed up by some concrete story or other information. As an example, the chapter "Spaghetti Dinner" presents a fictional example of a manager inviting a new team over for dinner, then having them buy and prepare the meal as a group, in order to produce a first team success. Other chapters use real-life stories or cite various studies to illustrate the principles being presented.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Scrum.org Professional Scrum Product Owner (PSPO I) Assessment Study Tips

Scrum.org Professional Scrum Product Owner (PSPO I) Assessment Study Tips | Devops for Growth | Scoop.it
Read and thoroughly understand/internalize the Scrum Guide. Read it several times in different sittings. We recommend that you download the PDF and read it like you would a book. Over, and over again! Take the Scrum Open assessment numerous times. Get to where you can take it 5 times in a row and score 100%…
Mickael Ruau's insight:

Assume that there are no “perfect” answers… Only “best” answers — when wearing your “Scrum Principles Wizard” hat. Answer as if you were the author of the Scrum Guide yourself.

No comment yet.