![SMT August 19.jpg](https://cdn.steemitimages.com/DQmWrh2U9TEdK2wkAmPZCBahbGBsZ2Ra5pRa8aQGg2thsNT/SMT%20August%2019.jpg)

<h1>Progress</h1>

Despite our focus on HF21 (one day away!), we hit our ideal velocity right on the nose. We completed 16 points and our ideal velocity is 15. This was one of the rare weeks where we had few unexpected distractions, which helped with productivity and consistency. 

![Screen Shot 2019-08-26 at 9.48.53 AM.png](https://cdn.steemitimages.com/DQmUjJq5TKHXQuUab5hRpXxBPTXv1KMPgmn1o2xVPuEQA4t/Screen%20Shot%202019-08-26%20at%209.48.53%20AM.png)

<h3>Completed Issues</h3>

We completed three issues ([#2746](https://github.com/steemit/steem/issues/2746), [#2747](https://github.com/steemit/steem/issues/2747), and [#3461](https://github.com/steemit/steem/issues/3461)). Issue 2746 implemented SMT Vesting semantics. Issue 2747 allows content creators to specify which SMTs they want to be able to vote on their content and the comment options for each SMT. Issue 3461 was some much needed cleanup work.

We are about a week ahead of schedule. This is great news with Hardfork 21 going live [tomorrow](https://steemit.com/hf21/@steemitblog/hardfork-21-survival-guide). While we do not expect any problems with the hardfork, the benefit of being ahead of schedule is that *even if* there are any difficulties which consume engineering time, we should not fall behind on SMT development. 

## Scope Increase

There was no additional scope increase this week.

## Summary

**Completed : 16**
**In Progress : 5**
**Scope Increase: 0**
**Net From Ideal: 14**
**Status: Good**

**[Read the previous SMT Burnup](https://steemit.com/smt/@steemitblog/smt-burn-up-refactor)** 
**[Learn more about SMT Burnup Methodology](https://steemit.com/smt/@steemitblog/smt-burnup-update-july)**

_The Steemit Blockchain Team_