5 Results for : triangulate

  • Thumbnail
    My Cruel Games: IMNarcEvil, Book 11 , Hörbuch, Digital, ungekürzt, 33min
    I am the narcissist. I will do whatever I want to whenever I want to do it. I will intimidate, triangulate, gaslight, abuse, and scare you at will. I will put you at the center of my friends and my family so that I can control your behavior from all sides and from all angles. You think that you have entered this relationship of your own free will. Not so. You have entered this relationship, and now you are not allowed to leave it before I feel it is time to discard you. I have put efforts into you, brought you around my inner circle, and I have graced you with my presence when I decided to have sex with you. I have already claimed you as mine in my mind and to my friends and family. I have already claimed you as my own indentured slave. I have claimed you so that you can do the lawn mowing, the cooking, the cleaning, the laundry, and running my errands. I have claimed you so that you can birth and raise my children for me, but only under my direct supervision. If you so choose to leave me before the children are fully transformed to narcissists in my own image, I will rip them away so that I can have someone else raise them in the way I want them raised. ungekürzt. Language: English. Narrator: Freudians Id. Audio sample: https://samples.audible.de/bk/acx0/107896/bk_acx0_107896_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    Narcissistic Fathers: Coping with the Self-Absorbed: Transcend Mediocrity, Book 200 , Hörbuch, Digital, ungekürzt, 23min
    Many people have grown up in broken homes. They often wonder for many years what went wrong. They don't feel like their childhood was happy, but they can't quite put their finger on what had caused the discontent. On the surface, their parents tried to make it look like everything was picture perfect. Other people outside of the family might even have believed it. The children often grow up blaming themselves for everything that went wrong at home. However, this is far from the truth. Once a person starts to dig into their childhood, they may begin to realize that at least one parent wasn't quite what he or she seemed. It was hard to differentiate which parent caused the discontent at home. A person's mother could seem chronically unhappy, depressed, and anxious. She might behave as though she is jealous, ungrateful, unappreciative, or critical. The truth isn't always what it seems. Sometimes the father is the actual culprit, but he is content to attribute the problems in the family to the disobedient children or nagging wife. Many people find out much later that it was really a narcissistic father that was at the root of all of the family's problems. The narcissistic father often causes the mother's steep mental decline by using "gaslighting" to break down her self-esteem. He isolates her from her friends and family, and often reacts in angry and jealous ways to her attempts to interact with coworkers or school personnel. He often doesn't support the mother or the children emotionally. The narcissistic father might triangulate the mother, or pit others against her to make her react in jealous ways or to destroy her self-confidence. He might be competing against the mother, always holding the family assets just out of arm's reach for her. She constantly has to fight him or beg him in order to provide things that the children need. ungekürzt. Language: English. Narrator: Pete Beretta. Audio sample: https://samples.audible.de/bk/acx0/064743/bk_acx0_064743_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    Narcissistic Fathers: High Expectation, Critical Putdowns and Broken Promises: Transcend Mediocrity, Book 141 , Hörbuch, Digital, ungekürzt, 23min
    Many of my listeners grew up in broken homes. They have wondered for many years what went wrong. They don't feel like their childhoods were happy, but they can't quite put their fingers on what caused the discontent. On the surface their parents tried to make it look like everything was picture perfect. Other people outside of the family might even have believed it. The children often grow up blaming themselves for everything that went wrong at home. However, this is far from the truth. Once people start to dig into their childhoods, they may begin to realize that at least one parent wasn't quite what he or she seemed. It was hard to differentiate which parent caused the discontent at home. A person's mother could seem chronically unhappy, depressed, and anxious. She might behave as though she is jealous, ungrateful, unappreciative, or critical. The truth isn't always what it seems. Sometimes the father is the actual culprit in a happy marriage, but he is content to attribute the problems in the family to the disobedient children or nagging wife. Many people find out much later that it was really a narcissistic father at the root of all of the family's problems. The narcissistic father often causes the mother's steep mental decline by using gaslighting to break down her self-esteem. He isolates her from her friends and family and often reacts in angry and jealous ways to her attempts to interact with coworkers or school personnel. He often doesn't support the mother or the children emotionally. The narcissistic father might triangulate the mother or pit others against her to make her react in jealous ways or to destroy her self-confidence. He might be competing against the mother, always holding the family assets just out of arm's reach for her. She constantly has to fight him or beg him in order to provide things that the children need. ungekürzt. Language: English. Narrator: Lori L. Parker. Audio sample: https://samples.audible.de/bk/acx0/060582/bk_acx0_060582_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    My Tactics: IMNarcEvil, Book 4 , Hörbuch, Digital, ungekürzt, 32min
    I am the narcissist. I have tactics to make you talk when I want you to talk. To make you shut up when I want you to shut up. To make you sit on reserve and wait around for me to come back. To make you stay faithful and loyal to me. To punish you when you betray me. To collect all of your resources. The Go-Getter All of my kind are taught from early on to get a "Go-Getter". This is a girl who works for resources, status, power, and money. I ride her coattails. I drop her off at work. I "go get her" when she is done working. Then, I take everything there is to take from her. I brag to all my friends that I have multiple Go-Getter girls lined up. One of them pays my phone bill. One of them supplies me with a place to live. One of them buys me my clothing so that I look fine when I am out picking up more girls. One of them pays my car insurance so that I can drive around in my sports car and be the envy of all the town. I got it made! My friends are envious of my skills and ability to suck resources off all these women that I am entangled with. I have sex with one girl at work in order to get that promotion that I want. I sit on the phone with her at home laughing so that the girl I am living with ramps up her efforts to please me and give me whatever it is that I want at home. This triangulation will cause jealousy in both girls, and will cause them to ramp up their positive attentions toward me, making me the center of their universe. Boy, do I feel like God! I triangulate my new love with my friends and my family members. I tell my friends that it is my new girl that is keeping me from spending any time with them. She is so controlling. She busts my balls when I want to go out. She is the reason that I can’t go out with the boys. My friends get jealous of her being in the primary position in my life. Then, I take her around my friends and watch the henpecking show begin. Each of them is fighting over yours tru ungekürzt. Language: English. Narrator: Gary Roelofs. Audio sample: https://samples.audible.de/bk/acx0/105297/bk_acx0_105297_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    User Stories Applied
    Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. A clear explanation of the most agile means of gathering software requirements Thoroughly reviewed and eagerly anticipated by the agile software development community Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application. Product Description Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach. Features + Benefits Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. ° A clear explanation of the most agile means of gathering software requirements ° Thoroughly reviewed and eagerly anticipated by the agile software development community ° Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins Backcover Agile requirements: discovering what your users really want. With this book, you will learn to: Flexible, quick and practical requirements that work Save time and develop better software that meets users' needs Gathering user stories -- even when you can't talk to users How user stories work, and how they differ from use cases, scenarios, and traditional requirements Leveraging user stories as part of planning, scheduling, estimating, and testing Ideal for Extreme Programming, Scrum, or any other agile methodology ---------------------------------------------------------------------------------------------------------- Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with user stories: simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other proxies Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach. ADDISON-WESLEY PROFESSIONAL Boston, MA 02116 www.awprofessional.com ISBN: 0-321-20568-5 Foreword. Acknowledgments. Introduction. I: GETTING STARTED. 1: An Overview. What Is a User Story? Where Are the Details? "How Long Does It Have to Be?" The Customer Team. What Will the Process Be Like? Planning Releases and Iterations. What Are Acceptance Tests? Why Change? Summary. Questions. 2: Writing Stories. Independent. Negotiable. Valuable to Purchasers or Users. Estimatable. Small. Testable. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 3: User Role Modeling. User Roles. Role Modeling Steps. Two Additional Techniques. What If I Have On-Site Users? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 4: Gathering Stories. Elicitation and Capture Should Be Illicit. A Little Is Enough, or Is It? Techniques. User Interviews. Questionnaires. Observation. Story-Writing Workshops. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 5: Working with User Proxies. The Users' Manager. A Development Manager. Salespersons. Domain Experts. The Marketing Group. Former Users. Customers. Trainers and Technical Support. Business or Systems Analysts. What to Do When Working with a User Proxy. Can You Do It Yourself? Constituting the Customer Team. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 6: Acceptance Testing User Stories. Write Tests Before Coding. The Customer Specifies the Tests. Testing Is Part of the Process. How Many Tests Are Too Many? The Framework for Integrated Test. Types of Testing. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 7: Guidelines for Good Stories. Start with Goal Stories. Slice the Cake. Write Closed Stories. Put Constraints on Cards. Size the Story to the Horizon. Keep the UI Out as Long as Possible. Some Things Aren't Stories. Include User Roles in the Stories. Write for One User. Write in Active Voice. Customer Writes. Don't Number Story Cards. Don't Forget the Purpose. Summary. Questions. II: ESTIMATING AND PLANNING. 8: Estimating User Stories. Story Points. Estimate as a Team. Estimating. Triangulate. Using Story Points. What If We Pair Program? Some Reminders. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 9: Planning a Release. When Do We Want the Release? What Would You Like in It? Prioritizing the Stories. Mixed Priorities. Risky Stories. Prioritizing Infrastructural Needs. Selecting an Iteration Length. From Story Points to Expected Duration. The Initial Velocity. Creating the Release Plan. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 10: Planning an Iteration. Iteration Planning Overview. Discussing the Stories. Disaggregating into Tasks. Accepting Responsibility. Estimate and Confirm. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 11: Measuring and Monitoring Velocity. Measuring Velocity. Planned and Actual Velocity. Iteration Burndown Charts. Burndown Charts During an Iteration. Summary. Developer Responsibilities. Customer Responsibilities. Questions. III: FREQUENTLY DISCUSSED TOPICS. 12: What Stories Are Not. User Stories Aren't IEEE 830. User Stories Are Not Use Cases. User Stories Aren't Scenarios. Summary. Questions. 13: Why User Stories? Verbal Communication. User Stories Are Comprehensible. User Stories Are the Right Size for Planning. User Stories Work for Iterative Development. Stories Encourage Deferring Detail. Stories Support Opportunistic Development. User Stories Encourage Participatory Design. Stories Build Up Tacit Knowledge. Why Not Stories? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 14: A Catalog of Story Smells. Stories Are Too Small. Interdependent Stories. Goldplating. Too Many Details. Including User Interface Detail Too Soon. Thinking Too Far Ahead. Splitting Too Many Stories. Customer Has Trouble Prioritizing. Customer Won't Write and Prioritize the Stories. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 15: Using Stories with Scrum. Scrum Is Iterative and Incremental. The Basics of Scrum. The Scrum Team. The Product Backlog. The Sprint Planning Meeting. The Sprint Review Meeting. The Daily Scrum Meeting. Adding Stories to Scrum. A Case Study. Summary. Questions. 16: Additional Topics. Handling NonFunctional Requirements. Paper or Software? User Stories and the User Interface. Retaining the Stories. Stories for Bugs. Summary. Developer Responsibilities. Customer Responsibilities. Questions. IV: AN EXAMPLE. 17: The User Roles. The Project. Identifying the Customer. Identifying Some Initial Roles. Consolidating and Narrowing. Role Modeling. Adding Personas. 18: The Stories. Stories for Teresa. Stories for Captain Ron. Stories for a Novice Sailor. Stories for a Non-Sailing Gift Buyer. Stories for a Report Viewer. Some Administration Stories. Wrapping Up. 19: Estimating the Stories. The First Story. Advanced Search. Rating and Reviewing. Accounts. Finishing the Estimates. All the Estimates. 20: The Release Plan. Estimating Velocity. Prioritizing the Stories. The Finished Release Plan. 21: The Acceptance Tests.The concept of user stories has its roots as one of the main tenets of ExtremeProgramming. In simple terms, user stories represent an effective means ofgathering requirements from the customer (roughly akin to use cases). Thisbook describes user stories and demonstrates how they can be used to properlyplan, manage, and test software development projects. The book highlightsboth successful and unsuccessful implementations of the concept, and providessets of questions and exercises that drive home its main points. After absorbingthe lessons in this book, readers will be able to introduce user stories in theirorganizations as an effective means of determining precisely what is required ofa software application.
    • Shop: buecher
    • Price: 31.99 EUR excl. shipping

Similar searches: