# Blog post about our new 'Shape up' template

**URL:** <https://community.fibery.io/t/blog-post-about-our-new-shape-up-template/2767>\
**Category:** News & Announcements\
**Created:** [May 4, 2022, 10:50am UTC](https://community.fibery.io/t/blog-post-about-our-new-shape-up-template/2767 "2022-05-04T10:50:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [May 4, 2022, 10:50am UTC](https://community.fibery.io/t/blog-post-about-our-new-shape-up-template/2767/1 "2022-05-04T10:50:38Z")

</div>

> **[Shape up with Fibery](https://fibery.io/blog/shape-up-with-Fibery/)**
>
> Using a 'fixed time, variable' scope development process, you can focus on delivering the most important features, according to a regular cycle.

---

<div class="post-metadata">

**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\
**Post date:** [May 5, 2022, 2:00pm UTC](https://community.fibery.io/t/blog-post-about-our-new-shape-up-template/2767/2 "2022-05-05T14:00:02Z")

</div>

This was interesting, but also makes me envy the team size some organizations have access to. It also reminded me that I have a decent amount of [EoS Traction Tools App](https://community.fibery.io/t/eos-traction-tools-app/1617) built out that I need to go back and revisit. I ended up running into little snags in the implementation that made me lose interest, but I think since then there have been some significant changes to explore using.

Overall, I think showing how fibery can implement various product development methodologies I think is a big benefit compared to the options that mostly implement some form of agile or kanban.