# How to approach QA in Shape Up

**URL:** <https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961>\
**Category:** Uncategorized\
**Created:** [March 16, 2022, 1:51pm UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961 "2022-03-16T13:51:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sashabrn](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sashabrn](https://discourse.learnshapeup.com/u/sashabrn)\
**Post date:** [March 16, 2022, 1:51pm UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961/1 "2022-03-16T13:51:28Z")

</div>

Hi All

How do you approach testing in Shape Up?  
When do your QAs start testing and when bugs reported are fixed?

---

<div class="post-metadata">

**Author:** ![jvillarejo](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.learnshapeup.com/jvillarejo/32/468_2.png) [@jvillarejo](https://discourse.learnshapeup.com/u/jvillarejo)\
**Post date:** [March 17, 2022, 7:55pm UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961/2 "2022-03-17T19:55:37Z")

</div>

QA testing and bugfixing is very reactive work.

Shape Up is for proactive and strategic work, not reactive work.

Reactive type of work it’s better done with a Kanban Board with different queues for statuses.

---

<div class="post-metadata">

**Author:** ![sashabrn](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sashabrn](https://discourse.learnshapeup.com/u/sashabrn)\
**Post date:** [March 18, 2022, 8:06am UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961/3 "2022-03-18T08:06:05Z")

</div>

It’s impossible to work in any methodology and have no bugs or testing at all, therefore in Shape Up people also will have bugs to be fixed or Pitches to be tested

---

<div class="post-metadata">

**Author:** ![shavin47](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.learnshapeup.com/shavin47/32/472_2.png) [@shavin47](https://discourse.learnshapeup.com/u/shavin47)\
**Post date:** [March 23, 2022, 6:13am UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961/4 "2022-03-23T06:13:13Z")

</div>

Hey have you checked out this chapter in Shape Up?

[https://basecamp.com/shapeup/3.5-chapter-14#qa-is-for-the-edges](https://basecamp.com/shapeup/3.5-chapter-14#qa-is-for-the-edges)

Basecamp does QA as well. They place a lot of responsibility on the designer and engineers to do basic quality work. However, for the edge cases, they do QA because it impacts thousands of customers. When a QA finds something he puts it into as a discovered task as a nice to have, and the designer triages it to decide if it is a must-have or just keep it as default. That’s the gist but the link has more.

---

<div class="post-metadata">

**Author:** ![Radu](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@Radu](https://discourse.learnshapeup.com/u/Radu)\
**Post date:** [July 19, 2022, 5:43am UTC](https://discourse.learnshapeup.com/t/how-to-approach-qa-in-shape-up/961/5 "2022-07-19T05:43:22Z")

</div>

It may depend on the project type: in our case we will probably add QA to the team of Builders, especially at the beginning of the 6 weeks. during this time they may decide what actions are needed for the QA (automation/manual/load tests) in order to have something delivered.  
It is just and idea… I didn’t do it yet.